Retrieve and validate a company's current registered agent information via OpenCorporates for cross-state consistency
domain: api.opencorporates.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
GET https://api.opencorporates.com/v0.4/companies/{jurisdiction_code}/{company_number}?api_token=YOUR_TOKEN&sparse=false
Extract registered_address fields and agent_name (where available in the jurisdiction data) from response.results.company
Compare the registered_address.country, registered_address.region, and registered_address.street_address across multiple jurisdiction registrations for the same group entity
Flag mismatches between the principal business address and registered address that could indicate an address discrepancy or stale filing
Use GET /v0.4/companies/{jurisdiction_code}/{company_number}/filings?api_token=YOUR_TOKEN to retrieve recent annual report filings confirming active good standing
Cross-reference the company.company_number with GLEIF's registered_as field to link the OpenCorporates record to any existing LEI
Known gotchas
Not all jurisdictions include registered agent name in their public registry data; many U.S. state SOS sources omit agent details in the OpenCorporates feed
OpenCorporates data is sourced from official registries but is not always current; freshness timestamps in response.results.company.retrieved_at indicate when the record was last fetched from the source
The sparse=false parameter returns additional fields including officers and filings counts but increases response size; use sparse=true for batch processing and only fetch full records when needed
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?