# Denbury Resources (Denbury Inc.) > Denbury Inc. was an independent oil and natural gas company headquartered in Plano, Texas, focused > on CO2 enhanced oil recovery across the Gulf Coast and Rocky Mountain regions and on carbon > capture, transport and sequestration through the largest CO2 pipeline network in the United > States. ExxonMobil acquired Denbury in November 2023; it now operates inside ExxonMobil's Low > Carbon Solutions business and deregistered its securities with the SEC on 2023-11-22. This file was GENERATED by API Evangelist on 2026-09-06 from the catalog record and the artifacts in this repository. Denbury publishes no llms.txt of its own — https://www.denbury.com/llms.txt returns HTTP 301 and no llms.txt document is served. ## What Denbury publishes Denbury runs no developer program: no developer portal, no API documentation, no SDKs, no CLI, no package-registry presence, no GitHub organization, no status page, no changelog, no pricing and no plans. The whole of /.well-known/ is refused at the origin with HTTP 403. The one machine-readable interface Denbury exposes is the WordPress core REST API behind its corporate website. It is anonymous, read-only and unmetered, and it is a content API — corporate, sustainability and carbon-solutions material — not an operational data feed. 276 routes across 14 namespaces are registered on the host; the twelve operations below are the ones that are both anonymously readable and useful. - Base URL: https://www.denbury.com/wp-json - Authentication: none for reads. Every documented route answers `Allow: GET` anonymously. - Rate limits: none documented and none signalled. Throttle conservatively. - Errors: WordPress `{code, message, data}` JSON envelope. Not RFC 9457. - Pagination: page / per_page (max 100) / offset, with X-WP-Total, X-WP-TotalPages and RFC 8288 Link. ## APIs - [Pages API](https://www.denbury.com/wp-json/wp/v2/pages): 48 published corporate pages — carbon solutions, EOR operations, the CO2 pipeline network, sustainability, owner relations, careers. - [Media API](https://www.denbury.com/wp-json/wp/v2/media): 432 media items — corporate presentations, ESG and corporate responsibility reports, PDFs and imagery. - [Search API](https://www.denbury.com/wp-json/wp/v2/search): full-text search over 105 indexed objects, returning id/title/url/type/subtype. - [Discovery API](https://www.denbury.com/wp-json/): registered content types, taxonomies and category terms — the self-describing surface. - [oEmbed API](https://www.denbury.com/wp-json/oembed/1.0/embed): oEmbed 1.0 documents for Denbury URLs. ## Operations - listPages — GET /wp/v2/pages - getPage — GET /wp/v2/pages/{id} - listMedia — GET /wp/v2/media - getMediaItem — GET /wp/v2/media/{id} - search — GET /wp/v2/search - listTypes — GET /wp/v2/types - getType — GET /wp/v2/types/{type} - listTaxonomies — GET /wp/v2/taxonomies - getTaxonomy — GET /wp/v2/taxonomies/{taxonomy} - listCategories — GET /wp/v2/categories - getCategory — GET /wp/v2/categories/{id} - getOembed — GET /oembed/1.0/embed ## The site is collapsing around the API Probed 2026-09-06: of the 48 pages the API publishes, **41 redirect to the homepage** when fetched at the `link` their own API record advertises. Only five resolve to themselves (home, contact, privacy policy, legal notices, terms). One 301s off-site to a jobs host that no longer resolves. The bodies are still there. `GET /wp/v2/pages/31` returns 17,650 characters of rendered HTML for "Carbon Solutions"; `GET /wp/v2/pages/1170` returns 17,233 for "Managing our Carbon Footprint". For 41 pages of Denbury's carbon-solutions, EOR, pipeline-network and sustainability material, this REST API is now the only public route to the content — the human site no longer serves it. Treat that as a wind-down signal, not a feature. ## Gated surfaces - /wp/v2/users — HTTP 403 at the origin. Author ids referenced by pages and media are not resolvable. - /wp-json/wp-abilities/v1/* — HTTP 401 rest_forbidden. The WordPress Abilities API namespace is registered but entirely auth-gated; its ability catalogue cannot be introspected anonymously. - context=edit on any route — HTTP 401 rest_forbidden_context. - /.well-known/* — HTTP 403 (nginx HTML) on every path probed. ## Specifications in this repository - openapi/denbury-resources-pages-api-openapi.yml - openapi/denbury-resources-media-api-openapi.yml - openapi/denbury-resources-search-api-openapi.yml - openapi/denbury-resources-discovery-api-openapi.yml - openapi/denbury-resources-oembed-api-openapi.yml All five are OpenAPI 3.2.0 and were DERIVED on 2026-09-06 from the server's own HTTP OPTIONS schema documents. They are API Evangelist artifacts, not Denbury publications. ## Other artifacts - authentication/denbury-resources-authentication.yml - conventions/denbury-resources-conventions.yml - errors/denbury-resources-problem-types.yml - data-model/denbury-resources-data-model.yml - conformance/denbury-resources-conformance.yml - lifecycle/denbury-resources-lifecycle.yml - rate-limits/denbury-resources-rate-limits.yml - plans/denbury-resources-plans-pricing.yml - packages/denbury-resources-packages.yml - security/denbury-resources-domain-security.yml - well-known/denbury-resources-well-known.yml - mcp/denbury-resources-mcp.yml (candidate; no server exists) - mcp/denbury-resources-tool-crosswalk.yml - skills/_index.yml ## Company links - Website: https://www.denbury.com/ - Contact: https://www.denbury.com/contact-us/ - Careers: https://www.denbury.com/careers/ - Terms: https://www.denbury.com/terms-and-conditions/ - Privacy: https://www.denbury.com/privacy-policy/ - SEC filings (CIK 0000945764): https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0000945764 - Acquisition announcement: https://corporate.exxonmobil.com/news/news-releases/2023/0713_exxonmobil-announces-acquisition-of-denbury - LinkedIn: https://www.linkedin.com/company/denbury-resources ## Caveat for agents This profile is maintained by API Evangelist, not by Denbury Inc. The API described here is a content API on a legacy corporate website inside an acquirer's estate. There is no SLA, no versioning policy, no deprecation notice mechanism and no support channel for it. Do not treat it as a supported integration surface.