POST /validate
Endpoints
POST /validate
Resolve a company string to a canonical entity.
POST
POST /validate
Use case
Resolve a company name from a customer email, chat message, or CRM record into a canonical BETA entity before calling other endpoints./validate is a fast cache lookup — call it first to avoid wasted lookups on unknown or low-confidence inputs.
Request
Company name to validate. Must be 2–200 characters.
Response
true if BETA resolved the input. Always check resolution.confidence alongside this — verified: true with low confidence means a fuzzy/fallback match, not a confident one.Confidence score (0–1) for the entity match.
Canonical entity record.
null when verified: false.Provenance metadata — see Citation Contract.
Present when
verified: false — explanation, e.g., "Company not found in database".Code samples
Live response
Errors
| Status | Body | When |
|---|---|---|
400 | {"error": "Company name required"} | Missing company field |
400 | {"error": "Company name must be 2-200 characters"} | Length out of range |
401 | {"error": "API key required"} | Missing Authorization header |
401 | {"error": "Invalid API key"} | Key not found or revoked |
429 | {"error": "Daily rate limit exceeded"} | Per-tier limit hit (see Pricing) |
Citation pointer
See Citation Contract for howresolution.source and resolution.confidence are populated — and why verified: true with resolution.source: "sec_fallback" is not the same trust signal as resolution.source: "curated".