OpenCorporates company API

Use the OpenCorporates company API to retrieve company-register identity and publicly available corporate information. Choose the documented selection using registry jurisdiction (jurisdiction), register or filing number (number); refine the result with supported source-page URL (url). Resolve a registered entity, compare legal names and inspect the corporate details published by its register. Fields restricted to signed-in source users may be null and listed in signed_in_only; public filing references do not imply document contents were downloaded. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (8)
Jurisdiction code, e.g. `gb`.
Company number in that register, e.g. `00445790`.
Instead of jurisdiction and number: the company's opencorporates.com/companies/... link.
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

{
  "addresses": [
    "TESCO HOUSE - DELAMARE RD, CHESHUNT, HERTFORDSHIRE EN8 9SL UK X0",
    "TESCO HOUSE, DELAMARE ROAD, CHESHUNT, HERTFORDSHIRE, EN8 9SL, United Kingdom"
  ],
  "agent_address": null,
  "agent_name": null,
  "alternative_names": [],
  "annual_return_last_made_up_date": "2016-06-07",
  "branch": null,
  "cached": false,
  "company_type": "Public Limited Company",
  "credits_used": 1,
  "dissolution_date": null,
  "filings_url": "https://opencorporates.com/companies/gb/00445790/filings",
  "government_approved_supplier": false,
  "inactive_officers_count": 62,
  "incorporation_date": null,
  "industry_codes": [
    "47.11: Retail sale in non-specialised stores with food, beverages or tobacco predominating (UK SIC Classification 2007)",
    "47.11: Retail sale in non-specialised stores with food, beverages or tobacco predominating (European Community NACE Rev 2)",
    "… 1 more"
  ],
  "jurisdiction": "gb",
  "jurisdiction_name": "United Kingdom",
  "latest_accounts_date": "2026-02-28",
  "name": "TESCO PLC",
  "number": "00445790",
  "officers_count": 11,
  "other_data": {},
  "other_identifiers": [
    {
      "type": "SEC CIK number",
      "url": "https://opencorporates.com/identifiers/cik/885834",
      "value": "885834"
    }
  ],
  "previous_company_numbers": null,
  "previous_names": [
    "TESCO STORES (HOLDINGS) PUBLIC LIMITED COMPANY",
    "TESCO STORES (HOLDINGS) LIMITED"
  ],
  "recent_filings": [],
  "register_entries": [
    {
      "label": "SEC Edgar entry",
      "value": "register id: 885834"
    },
    {
      "label": "UK Data Protection Register entry",
      "value": "register id: Z7055743"
    }
  ],
  "registered_address": {
    "lines": [
      "Tesco House, Shire Park Kestrel Way",
      "Welwyn Garden City",
      "… 2 more"
    ],
    "text": "Tesco House, Shire Park Kestrel Way, Welwyn Garden City, AL7 1GA, United Kingdom"
  },
  "signed_in_only": [
    "Incorporation Date",
    "Directors / Officers",
    "… 1 more"
  ],
  "status": "Active",
  "tax_numbers": [],
  "telephone_numbers": [],
  "url": "https://opencorporates.com/companies/gb/00445790",
  "websites": []
}

Response result

Response structure

Inferred from examples
  • addressesstring[]
  • agent_addressnull
  • agent_namenull
  • alternative_namesunknown[]
  • annual_return_last_made_up_datestring
  • branchnull
  • cachedboolean
  • company_typestring
  • credits_usedinteger
  • dissolution_datenull
  • filings_urlstring
  • government_approved_supplierboolean
  • inactive_officers_countinteger
  • incorporation_datenull
  • industry_codesstring[]
  • jurisdictionstring
  • jurisdiction_namestring
  • latest_accounts_datestring
  • namestring
  • numberstring
  • officers_countinteger
  • other_dataobject
  • other_identifiersobject[]
    • typestring
    • urlstring
    • valuestring
  • previous_company_numbersnull
  • previous_namesstring[]
  • recent_filingsunknown[]
  • register_entriesobject[]
    • labelstring
    • valuestring
  • registered_addressobject
    • linesstring[]
    • textstring
  • signed_in_onlystring[]
  • statusstring
  • tax_numbersunknown[]
  • telephone_numbersunknown[]
  • urlstring
  • websitesunknown[]

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use OpenCorporates company API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.