RICON — Rise of the Icon

API Documentation

Verified biographical data via REST API. Every response is structured for provenance, reviewability, and downstream partner trust.

API calls / month

1.2M

Uptime

99.97%

Avg latency

42 ms

Active consumers

Search endpoints

GET/v1/talent/{id}

Retrieve a verified talent profile with provenance metadata and module status.

Example request

curl --request GET \
  --url https://api.ricon.com/v1/talent/jk_001 \
  --header "Authorization: Bearer rk_sbx_7e18...5fd1"

Live JSON Preview Controls

Include provenanceInclude audit blockCompact JSON

Live JSON preview

{
  "id": "jk_001",
  "name": "Jason Kidd",
  "status": "verified",
  "modules": [
    {
      "type": "biography",
      "version": "3.2",
      "signed_at": "2026-03-12",
      "hash": "0x7f3a..."
    }
  ]
}

API key management (mock)

Mock key flow mirrors production patterns: generate scoped keys, store securely, rotate regularly, and monitor endpoint-level usage for abuse.

Usage and integration model

RICON API responses are designed for verified content systems. Build clients around source-aware objects, review states, and explicit version boundaries.

Send API key in Authorization header: Bearer <key>

Cache list endpoints for 60s and fetch profile endpoints on-demand

Persist module version/hash to detect upstream updates

Display source and reliability metadata in downstream UIs

Open API access form

{ "id": "jk_001", "name": "Jason Kidd", "status": "verified", "modules": [ { "type": "biography", "version": "3.2", "signed_at": "2026-03-12", "hash": "0x7f3a..." } ] }