Routescan

Routescan is a company surfaced via the API Evangelist harvest backlog (source: new-submission) and added to the network as a stub for full-pipeline profiling.

Routescan publishes 1 API contract indexed on the APIs.io network. Tagged areas include Company.

The Routescan catalog on APIs.io includes 1 Spectral governance ruleset.

Routescan’s developer surface includes pricing, getting-started guide, documentation, authentication, and 9 more developer resources.

🌐 Visit website📡 Profile data on GitHub
21.7/100 emerging ▬ flat Agent 7/100 agent aware Full breakdown ↓
scored 2026-11-01 · rubric v0.26.0 · Show this score on your site →
1 published contract
Company

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-01 · rubric v0.26.0
Composite quality — 21.7/100 · emerging
Contract Quality 0.0 / 19
Developer Ergonomics 5.0 / 15
Access Clarity 4.7 / 15
Operational Transparency 0.5 / 10
Contract Governance 1.6 / 9
Discoverability 3.9 / 8
Regulatory Posture 3.7 / 15
Create-or-Update Ergonomics 0.0 / 10
Agent readiness — 7/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Pagination 5 / 5
Distinct Operations 3 / 3
MCP Tool Quality 6 / 6
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Routescan It updates itself when the score changes. Paste this where you link to your API docs: 
<a href="https://apis.io/providers/routescan/"><img src="https://apis.io/badge/routescan/card.svg" alt="Routescan on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
10 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/routescan/apis.yml: open an issue on github.com/api-evangelist/routescan to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Routescan API

Routescan multi-chain explorer API

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Routescan API Rules

8 rules · 6 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Routescan Openapi Overlay

0 actions · update

UNRECORDED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Routescan Authentication

apiKey · 1 scheme

SECURITY

Routescan Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Routescan Agentic Access

99 operations · 3 acting

99 operations · 3 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted
GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation
Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

Authentication
Authentication
 DomainSecurity
DomainSecurity

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Pricing
Pricing

Company 1

The organization behind the API

Website
Website

Other 2

Properties that don't map to a standard resource type

Hosts
Hosts
 Vendors
Vendors

Source (apis.yml)

apis.yml Raw ↑ 
aid: routescan
name: Routescan
description: 'Routescan is a company surfaced via the API Evangelist harvest backlog (source: new-submission) and added to
  the network as a stub for full-pipeline profiling.'
url: https://raw.githubusercontent.com/api-evangelist/routescan/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-27 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-27'
modified: '2026-10-27'
tags:
- Company
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Conformance
  url: conformance/routescan-conformance.yml
- type: LLMsTxt
  url: llms/routescan-llms.txt
- type: Hosts
  url: hosts/routescan-hosts.yml
- type: Vendors
  url: vendors/routescan-vendors.yml
- type: TermsOfService
  url: https://routescan.io/terms-of-use
- type: PrivacyPolicy
  url: https://routescan.io/privacy
- type: Pricing
  url: https://routescan.io/pricing
- type: GettingStarted
  url: https://docs.routescan.io/getting-started/supported-chains
- type: Documentation
  url: https://docs.routescan.io/
- type: GitHubOrganization
  url: https://github.com/routescan
- type: Authentication
  url: authentication/routescan-authentication.yml
- type: DomainSecurity
  url: security/routescan-domain-security.yml
- type: Website
  url: https://routescan.io/
apis:
- name: Routescan API
  description: Routescan multi-chain explorer API
  humanURL: https://docs.routescan.io/api
  baseURL: https://api.routescan.io
  aid: routescan:routescan-api
x-submission-probe: 403, 2026-10-26
x-coverage:
  state: blocked
  reason: bot-challenge
  detail: Website https://routescan.io/ returned 403, likely bot challenge
  evidence:
  - url: https://routescan.io/
    status: 403
x-enrichment:
  date: '2026-10-27'
  status: enriched
  artifacts_added: 11
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Routescan API — frequently asked questions

Does Routescan have an API?

Yes. APIs.io lists 1 API from Routescan, including Routescan API.

How do I authenticate with the Routescan API?

Routescan uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Routescan Authentication.

Is the Routescan API ready for AI agents?

Routescan has a Kin Score of 21.7 out of 100 (emerging) and an Agent Readiness score of 7.2 (agent-aware), scored by API Evangelist on 2026-11-01.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/routescan"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/routescan/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/routescan/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.