ExchangeRebel Bridge Scorer API

The Bridge Scorer API from ExchangeRebel — 4 operation(s) for bridge scorer.

GitHub OpenAPI

Operations 4

POST /toll/bridge/score Score a bridge by security, liquidity, and incidents #
GET /toll/bridge/bridges All bridges scored, best first (free) #
GET /toll/bridge/incidents Bridge incident database (free) #
GET /toll/bridge/health Check the bridge risk service status #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/exchangerebel-com:exchangerebel-com-bridge-scorer-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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

OpenAPI Specification

exchangerebel-com-bridge-scorer-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: ExchangeRebel — pay-per-call APIs for AI agents (x402 on…
  version: 1.0.0
  contact:
    name: 'ExchangeRebel (operator: Rebel Data)'
    url: https://exchangerebel.com
    email: sound.money.investing@gmail.com
  x-guidance: 'All paid operations use x402 on Solana: call without payment to get a 402 challenge (SOL recipient + USDC token account + fresh memo), pay with the memo attached via the Solana Memo program, then retry with header X-Payment-Tx: <signature> and ?toll_memo=<memo>. Challenges are dual-version: the PAYMENT-REQUIRED header carries the x402 v2 PaymentRequired object and the response body carries the same challenge in x402 v1 form for compatibility. Free operations (security: []) include each service''s /health catalog with full response shapes. Prices in x-payment-info are USD per call unless the summary says otherwise (RPC is per 1,000-request block; Telegram provisioning is per bot-month; transcription is per minute of audio).'
  description: '67 data and utility APIs behind x402 tolls, settled in SOL or USDC on Solana. Call a paid endpoint without payment to receive a 402 x402 challenge (recipient + fresh memo), pay with the memo attached via the Solana Memo program, then retry with the X-Payment-Tx header and toll_memo query parameter. Free catalog/health endpoints are marked without x-payment-info. Full catalogs: GET /toll/discovery and each service''s /health.'
servers:
- url: https://exchangerebel.com
tags:
- name: Bridge Scorer
paths:
  /toll/bridge/score:
    post:
      tags:
      - Bridge Scorer
      summary: Score a bridge by security, liquidity, and incidents
      responses:
        '200':
          description: Success. Response shape is documented in the service catalog (GET /health on the service).
          content:
            application/json:
              example:
                bridge:
                  id: cctp
                  name: Circle CCTP
                route:
                  from_chain: ethereum
                  to_chain: base
                  token: USDC
                  amount_usd: 10000
                score: 81
                risk_level: low
                factors:
                - name: base
                  impact: 50
                  detail: Neutral starting point; evidence moves it up or down.
                - name: maturity
                  impact: 8
                  detail: '3 years in production: meaningful track record.'
                - name: tvl
                  impact: 8
                  detail: 'No pooled TVL to attack: burn-and-mint has no honeypot to drain.'
                - name: security_model
                  impact: 10
                  detail: 'native_burn_mint: Native burn-and-mint: no wrapped IOUs, no custodied pool to drain.'
                - name: clean_record
                  impact: 5
                  detail: 'Zero recorded incidents over 3 years: clean operational record.'
                - name: flag:centralization
                  impact: -3
                  detail: 'Centralized attestation: liveness and honesty depend on one operator.'
                - name: amount_vs_tvl
                  impact: 0
                  detail: 'Burn-and-mint model: no pooled TVL to concentrate against.'
                - name: token
                  impact: 3
                  detail: 'USDC is natively supported (burn-and-mint): no wrapped IOU risk.'
                recommendation: Proceed with standard caution. Circle CCTP scores as low risk for this route.
                alternatives: []
                disclaimer: Risk assessment, not financial advice. Scores reflect public data and heuristics; they do not guarantee safety. Verify independently before moving funds.
                inputs_summary:
                  sources:
                  - bridge registry
                  - incident database
                  bridge_incidents_considered: 0
                  factors_scored: 8
                paid_via: payai
                envelope:
                  v: 1
                  service: bridge-scorer
                  source: bridge registry + incident database (KV, seed fallback)
                  grade: derived
                  changes:
                    supported: false
        '402':
          description: 'Payment Required (x402). The PAYMENT-REQUIRED response header carries the x402 v2 PaymentRequired object (base64 JSON: scheme, CAIP-2 network, amount, asset, payTo, plus the bazaar discovery extension); the response body carries the same challenge in x402 v1 form for compatibility, naming the SOL recipient and USDC token account on Solana plus a fresh memo. To pay on this service''s rail: pay with the memo attached (Solana Memo program), then retry with header ''X-Payment-Tx: <transaction signature>'' and query parameter ''toll_memo=<memo>''.'
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                bridge:
                  type: string
                  description: string
                from_chain:
                  type: string
                  description: string
                to_chain:
                  type: string
                  description: string
                token:
                  type: string
                  description: string
                amount_usd:
                  type: number
                  description: number
      x-payment-info:
        protocols:
        - x402
        price:
          mode: fixed
          currency: USD
          amount: '0.01'
      security:
      - x402Payment: []
      operationId: postTollBridgeScore
      x-operation-id-source: derived
  /toll/bridge/bridges:
    get:
      tags:
      - Bridge Scorer
      summary: All bridges scored, best first (free)
      responses:
        '200':
          description: Success. Response shape is documented in the service catalog (GET /health on the service).
      security: []
      operationId: getTollBridgeBridges
      x-operation-id-source: derived
  /toll/bridge/incidents:
    get:
      tags:
      - Bridge Scorer
      summary: Bridge incident database (free)
      responses:
        '200':
          description: Success. Response shape is documented in the service catalog (GET /health on the service).
      security: []
      operationId: getTollBridgeIncidents
      x-operation-id-source: derived
  /toll/bridge/health:
    get:
      tags:
      - Bridge Scorer
      summary: Check the bridge risk service status
      responses:
        '200':
          description: Success. Response shape is documented in the service catalog (GET /health on the service).
      security: []
      operationId: getTollBridgeHealth
      x-operation-id-source: derived
components:
  securitySchemes:
    x402Payment:
      type: apiKey
      in: header
      name: X-Payment-Tx
      description: 'x402 toll payment proof: the Solana transaction signature of a payment carrying the memo from the 402 challenge; send together with ?toll_memo=<memo>. Payment itself is made on-chain in SOL or USDC to the recipient named in the challenge.'