{"slug":"metadata-coverage","title":"Best crypto data API for token metadata, live across Mobula, Codex, Jupiter","subtitle":"Share of metadata fields (logo, description, twitter, website) populated for fresh-launch tokens, audited every launch on Solana, BNB and Base.","category":"Aggregators","metric":"Field coverage","unit":"pct","status":"live","higherIsBetter":true,"filters":null,"value":34.7222,"leader":{"name":"Codex","slug":"codex","value":34.7222},"rankings":[{"name":"Codex","slug":"codex","ms":{"p50":34.7222,"p90":59.8684,"p99":94.25,"mean":32.1799},"successRate":100,"sampleSize":1156.2},{"name":"Mobula","slug":"mobula","ms":{"p50":11.3971,"p90":48.2292,"p99":66.649,"mean":23.0969},"successRate":100,"sampleSize":1156.2}],"sparkline":[56.7308,31.25,33.3333,27.5,32.5,20.2381,12.5,9.09091,43.75,29.1667,36.0294,37.1795,36.3095,33.9286,23.5294,24.2647,32.2222,37.7778,53.2258,51.1905,50,33.3333,50,28.8462,28.8462,28.8462,0,21.6667,19.1176,19.1176,0,35.7143,50,58.3333,100,50,0,0,23.0769,23.0769,5.76923,0,0,25,75,75,53.125,47.2222,52.5,60.7143,65.3846,60,50,50,50,50,0,0,0,0,8.33333,15.9091,23.3333,31.6667,41.6667,47.5,40.9091,33.3333,25,34.7222,39.0625,36.7647],"sampleSize":3024.523,"asOf":"2026-08-15T10:24:01.549Z","headline":"Codex leads field coverage at 34.7% (24h avg) on Best crypto data API for token metadata, live across Mobula, Codex, Jupiter.","quote":"Codex leads field coverage at 34.7% (24h avg) on Best crypto data API for token metadata, live across Mobula, Codex, Jupiter. Source: OpenChainBench (https://openchainbench.com/benchmarks/metadata-coverage).","cite":{"plain":"OpenChainBench. \"Best crypto data API for token metadata, live across Mobula, Codex, Jupiter\". Retrieved 2026-08-15. https://openchainbench.com/benchmarks/metadata-coverage","bibtex":"@misc{ocb_metadata_coverage,\n  author = {OpenChainBench},\n  title  = {Best crypto data API for token metadata, live across Mobula, Codex, Jupiter},\n  year   = {2026},\n  url    = {https://openchainbench.com/benchmarks/metadata-coverage},\n  note   = {Retrieved 2026-08-15}\n}","apa":"OpenChainBench. (2026). Best crypto data API for token metadata, live across Mobula, Codex, Jupiter. Retrieved August 15, 2026, from https://openchainbench.com/benchmarks/metadata-coverage","ris":"TY  - GEN\r\nAU  - OpenChainBench\r\nTI  - Best crypto data API for token metadata, live across Mobula, Codex, Jupiter\r\nPY  - 2026\r\nUR  - https://openchainbench.com/benchmarks/metadata-coverage\r\nY2  - 2026-08-15\r\nER  - \r\n"},"pageUrl":"https://openchainbench.com/benchmarks/metadata-coverage","ogImage":"https://openchainbench.com/api/og/metadata-coverage","source":"https://github.com/ChainBench/OpenChainBench/tree/main/harnesses/metadata-coverage","methodology":["Token discovery: Mobula Pulse V2 WebSocket on `solana`, `evm:56` (BNB), `evm:8453` (Base) for known launchpads (pump.fun, Meteora DBC, Four.meme, Raydium CPMM, Zora, BaseApp, Bags, Moonshot).","Coverage check: for each fresh token, query each aggregator's metadata endpoint and record whether `logo`, `description`, `twitter` and `website` are populated.","Aggregators in scope: Mobula (`/api/2/token/details`), Codex (GraphQL `token` query, JWT-authenticated), Jupiter (`/v6/tokens/<mint>`, Solana only).","Cadence: queue-driven; every newly-discovered token is checked once across the three aggregators. Steady-state ≈ several hundred checks per provider per hour.","Region: single probe origin (one monitor instance on our infrastructure). The bench intentionally declares no region dimension; multi-region would require additional monitor instances and is not currently planned.","Ratio: `metadata_coverage_success_total / metadata_coverage_checks_total`, expressed in percent. Failures of the metadata API itself (timeouts, 5xx) are not counted in the denominator. only successful responses with the field check applied.","Jupiter is Solana-only. it appears with zero coverage on EVM chains by construction; the cross-chain headline excludes Jupiter on chains it does not support."],"license":"CC-BY-4.0"}