For Builders

Cite claims programmatically. Verify cryptographically.

SupaDrop exposes preserved financial claims through read-only interfaces. Every record includes source provenance and verification data.

GET /claims/7a8f2e1d
{
"claim_id": "7a8f2e1d",
"content": "Revenue grew 6 percent...",
"source": {
"transcript": "AAPL_Q4_2024",
"offset": [8432, 8591]
},
"timestamp": "00:14:23.840",
"speaker": "Timothy Cook",
"hash": "7a8f2e1d4c3b..."
}
✓ Read-only access
✓ Cryptographically verifiable

Access methods

Read-only API

ClaimBlocks are queryable by ID, company, date, or metric. All endpoints are read-only.

Hash verification

Claim integrity is verifiable by comparing content hash against source document.

Source attribution

Every response includes transcript coordinates, timestamps, and speaker attribution.

Immutable records

Claims cannot be modified. Attempts to alter records are cryptographically detectable.

API endpoints

GET/claims/:id
Retrieve specific claim by permanent identifier.
GET/claims
Query claims by company and time period.
GET/transcripts/:id
Retrieve full earnings call transcript with claim markers.
GET/verify/:claim_id
Verify claim hash against source document.

Response structure

Claim record

JSON
{
"claim_id": "7a8f2e1d",
"content": "...",
"source": { ... },
"timestamp": "00:14:23.840",
"hash": "7a8f2e1d..."
}

Required fields

claim_id
Permanent identifier for this claim
content
Exact text as spoken in earnings call
source
Transcript identifier and character offsets
timestamp
Millisecond-precision audio timestamp
hash
SHA-256 content hash for verification

System constraints

Read-only access

ENFORCED

All API endpoints are GET requests. No write, update, or delete operations exist.

Immutable records

ENFORCED

Preserved claims cannot be modified. Hash verification detects any alteration attempts.

No processing

ENFORCED

API returns preserved records only. No analysis, aggregation, or transformation occurs.

Source fidelity

ENFORCED

Every claim includes exact character offsets to original transcript. Verification is always possible.

Integration patterns

Citation in analysis

Reference claims by permanent ID in financial models or reports. Include hash for verification.

Automated verification

Periodically verify claim hashes against source documents to ensure integrity.

Audit trail construction

Build audit logs that reference preserved claims with cryptographic proof of authenticity.

Comparative analysis

Query claims across quarters to track changes in company statements over time.