API reference · v0.1 draft
Compute trust data, by API.
Verify counterparties, read registered clusters and contracts, follow performance over the life of a loan and, as they publish, pull Price Reference and Loss Index data. Everything is keyed to Synpute IDs.
- Base URL
- https://api.synpute.com
- Format
- JSON · OpenAPI 3.1
- Auth
- Bearer key, scoped
- Version
- 0.1.0-draft
Before your first request
Authentication
Every request sends a secret key as a bearer token. Keys are scoped (verify:read, registry:read, monitor:read and so on) and issued per environment. Test keys return sample data only.
Identifiers
Synpute IDs are the primary keys: SYN-CL- clusters, SYN-OP- operators, SYN-BY- buyers, SYN-CT- contracts. Records follow the Synpute Standard.
Access
You only see what an operator has shared with you. Contracts and performance are visible to the lenders and parties the operator grants, and every read is logged on the record.
Conventions
Errors share one shape: a code, a human message and a request ID. Lists paginate by cursor. Rate limits are per key and returned in response headers.
{
"error": {
"code": "not_found",
"message": "No cluster with ID SYN-CL-0000.",
"request_id": "req_7Hk2"
}
}Endpoints
Entities
Operators, buyers, lenders and platforms.
Clusters
GPU clusters and their units, in the Synpute Standard.
Contracts
Capacity sold to buyers, with step-in terms.
Verifications
Check counterparties and assets once; reuse the result.
Credit Profiles
Diligence on buyer, asset and contract, with risk indicators.
Monitoring
Telemetry, payments, covenants, alerts and reports.
Transfers
Programs and lender-directed transitions.
Request access
Preview endpoints are open to a small group of marketplaces, exchanges and lenders. Tell us what you'd integrate and when; we'll send test keys and the pilot terms.
Draft reference. Endpoints, fields and scopes may change before v1. Examples use illustrative data. Synpute returns verified facts and risk indicators; it does not issue credit ratings or investment advice.