POST /corroborate
Endpoints
POST /corroborate
Verify a factual claim against SEC + news + people index.
POST
POST /corroborate
Use case
Verify a factual claim about a company against BETA’s structured sources (SEC filings, M&A transactions, material events, news, people index) before your agent acts on it. Returnscorroborated: true with evidence + confidence, or corroborated: false with reason: "no_match" when sources don’t support the claim. This is the citation-discipline primitive — treat corroborated: false as informational, not as failure.
For the standard integration pattern, see Recipes → Corroborate before write.
Request
Company name or entity key. 2–200 characters.
Array of 1–10 claim objects. Each claim:
Response
Resolved entity (
key, name, verified).One result per submitted claim, indexed by
claim_index.sources_available, entity_coverage (public_company | private_company), corroborated_at (ISO timestamp), resolution (per Citation Contract).Code samples
Live response
Cost notes
/corroborate is BETA’s most expensive call (0.05 for the others). Batch up to 10 claims per request to minimize round-trip cost and latency.
Errors
| Status | Body | When |
|---|---|---|
400 | {"error": "At least one claim required"} | Empty claims array |
400 | {"error": "Maximum 10 claims per request"} | claims.length > 10 |
404 | {"error": "Company not found", "code": "NOT_FOUND"} | No entity resolved |
Citation pointer
See Citation Contract for howcorroborated: false is the explicit refusal signal — the most important shape this endpoint produces.