Developers

Assessments as structured data.

The same intelligence behind every Qrypt report, designed for applications and autonomous agents. The API is in design and not yet publicly available.

01Planned API

Endpoints Planned

GET/v1/scan/tokenAssess a token contract.
GET/v1/scan/walletAnalyze an account's type, signing mechanism and key exposure.
GET/v1/scan/contractAnalyze a non-token contract.
GET/v1/asset/scoreLatest score, coverage and confidence for an indexed asset.
GET/v1/asset/historyEvery past assessment of an asset, oldest to newest.
GET/v1/quantum/readinessCryptographic dependencies and migration status for a network.

Example responseIllustrative

{
  "asset": "0x…",
  "chain": "robinhood",
  "security": {
    "score": 78,
    "coverage": 100,
    "confidence": "medium",
    "model_version": "1.0"
  },
  "quantum": {
    "status": "conventional_cryptography",
    "evidence": []
  },
  "findings": [],
  "assessed_at": "2026-10-10T12:00:00Z"
}

02Design requirements

What every response will carry

Versioned responses: Every path is versioned; breaking changes ship under a new version.
Stable schemas: Fields are added, never repurposed.
Evidence references: Each finding points to the contract or transaction it was read from.
Assessment timestamps: Responses state when evidence was collected, and flag stale data.
Scoring model version: The model that produced a score is always named.
Data coverage: The share of the model that had evidence is reported with every score.
Rate limiting: Limits and remaining quota are returned in response headers.
Error handling: Errors use stable machine-readable codes with a human-readable message.

03x402

Pay-per-request for agents Planned

Agents will be able to request an assessment and pay for that single call over HTTP, without an account or API key. This integration has not been built. Paid access is not available and nothing here is an offer of service.

Methodology is public today: read the scoring model.

Per-request pricingNot built
Usage receiptsNot built
Payment verificationNot built
Request limitsNot built
Settlement reportingNot built

Endpoints Planned

GET/v1/scan/tokenAssess a token contract.

GET/v1/scan/walletAnalyze an account's type, signing mechanism and key exposure.

GET/v1/scan/contractAnalyze a non-token contract.

GET/v1/asset/scoreLatest score, coverage and confidence for an indexed asset.

GET/v1/asset/historyEvery past assessment of an asset, oldest to newest.

GET/v1/quantum/readinessCryptographic dependencies and migration status for a network.

{ "asset": "0x…", "chain": "robinhood", "security": { "score": 78, "coverage": 100, "confidence": "medium", "model_version": "1.0" }, "quantum": { "status": "conventional_cryptography", "evidence": [] }, "findings": [], "assessed_at": "2026-10-10T12:00:00Z" }

What every response will carry

Versioned responses

Every path is versioned; breaking changes ship under a new version.

Stable schemas

Fields are added, never repurposed.

Evidence references

Each finding points to the contract or transaction it was read from.

Assessment timestamps

Responses state when evidence was collected, and flag stale data.

Scoring model version

The model that produced a score is always named.

Data coverage

The share of the model that had evidence is reported with every score.

Rate limiting

Limits and remaining quota are returned in response headers.

Error handling

Errors use stable machine-readable codes with a human-readable message.