Concho Resources
Concho Resources, Inc. was an independent oil and natural gas company focused on the acquisition, development, exploration, and production of oil and natural gas properties primarily in the Permian Basin of West Texas and southeast New Mexico. On January 15, 2021, ConocoPhillips completed an all-stock acquisition of Concho Resources at a total enterprise value of $13.3 billion, retiring the Concho brand. This profile is preserved as a historical record; Concho no longer operates under this name and never published any public developer APIs.
Concho Resources is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Concho Resources was absorbed by ConocoPhillips on 2021-01-15 and the brand retired; conchoresources.com now answers every path — including /openapi.json, /llms.txt and all seven probed /.well-known/ documents — with a blanket HTTP 302 to https://www.conocophillips.com/, and api./developer./docs.conchoresources.com are NXDOMAIN.
This is an honest zero, not a gap in our research. Concho Resources does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://conchoresources.com/→ HTTP 302https://conchoresources.com/openapi.json→ HTTP 302https://conchoresources.com/.well-known/api-catalog→ HTTP 302https://conchoresources.com/.well-known/agent-card.json→ HTTP 302https://www.conocophillips.com/news-media/story/conocophillips-completes-acquisition-of-concho-resources/→ HTTP 200
Resources
Every other property we hold for Concho Resources — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Concho Resources is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/concho-resources · machine-readable index on apis.io
This is an independent, third-party profile of Concho Resources, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.