Build on the
economic identity graph.
ENTIA turns governed observations into canonical economic identity. One graph; multiple machine-ready projections for agents, applications, grounding and evidence-driven workflows.
Live platform state
runtimeRegistry corpus figures are loaded from GET /api/v1/stats/live. Entia Home launch scope is a separate product-generation metric derived from the canonical generator matrix.
Corpus source: get_platform_stats · Home scope source: scripts/nodealpha/country_matrix.json → home_launch_countries · loading…
One graph. Multiple projections.
ENTIA is not a static dataset or directory. Observations are resolved into governed claims on a canonical economic-identity graph, then projected for different machine-consumption paths.
Choose your interface
MCP · AGENTS
Native tools for AI systems
Streamable HTTP at https://mcp.entia.systems/mcp. tools/list is authoritative for the current schema.
REST v3 · APPLICATIONS
Same capabilities over HTTP
Customer integrations use /api/v1/v3/*. Historical internal paths are not the customer contract.
Capability matrix
Current MCP inventory: 12 tools. Runtime tools/list remains authoritative.
| Capability | MCP tool | HTTP surface | Access |
|---|---|---|---|
| Entity resolution | entity_lookup | /api/v1/v3/entity_lookup | Public preview / key |
| Entity search | search_entities | /api/v1/v3/search_entities | Public preview / key |
| VAT validation | verify_vat | /api/v1/v3/verify_vat | Public preview / key |
| Territorial context | zone_profile | /api/v1/v3/zone_profile | SIGNAL+ |
| Competitor context | get_competitors | /api/v1/v3/get_competitors | BUILD+ |
| Curated examples | get_showcase | /api/v1/v3/get_showcase | Public |
| Professional registry | professional_lookup | /api/v1/v3/professional_lookup | Enterprise + DPA |
| Full dossier | get_full_dossier | /api/v1/v3/full_dossier | INTEGRATE+ |
| Platform state | get_platform_stats | /api/v1/stats/live | Public |
| Risk audit | run_risk_audit | /api/v1/v3/run_risk_audit | SIGNAL+ |
| Entia Home JSON-LD | get_entia_home | /v1/identity/{cc}/{sector}/{city}/{slug}.jsonld | Public |
| Home projection snapshot | get_entity_home_projection | Projection contract | SIGNAL+ |
Entity resolution
Resolution is the core operation: multiple identifiers and observations converge on a canonical entity before downstream projections are produced.
INPUTS
Company name · VAT / CIF / NIF · LEI · domain · canonical URL · country · national registry identifier.
OUTPUT
Canonical entity · identifiers · corroborating sources · verification state · provenance · territorial context · machine projections.
Evidence, provenance & assurance
A claim is more useful than a generic “verified” label when its origin and observation context travel with it.
tools/list, the REST reference and machine-readable manifests as the contract; do not infer fields from this illustrative shape.Authentication & operational contract
CUSTOMER AUTH
HTTP header names are case-insensitive. X-ENTIA-API-KEY is a different internal header and is not the customer credential.
MACHINE CONTRACTS
/.well-known/api-catalog/.well-known/mcp.json/.well-known/ai-pricing.json/.well-known/entia-home-scope.jsontools/list
Operational semantics
MEASUREMENT BOUNDARY
Machine access ≠ retrieval ≠ citation ≠ answer inclusion ≠ commercial action. Each event needs its own evidence. Crawling or access does not demonstrate model training.
EVIDENTIAL BOUNDARY
An ordinary API response is not by itself an electronic seal or qualified timestamp. Separate forensic workflows may archive and timestamp evidential records under their own chain-of-custody process.
Start building
Applications
Use the REST v3 surface with x-entia-key and the same canonical capabilities.