54ch10

54ch10 serves pre-interact risk briefs for wallet addresses, tokens and URLs — phishing, scam, honeypot and URL-reputation heuristics an agent can call BEFORE it signs, approves, bridges or opens a dapp URL. A brief returns a 0–100 score where higher is more concerning, a band, flags, a summary and the sources behind it, so a caller can gate its next tool call on policy: refuse on critical, require human confirmation on elevated. The provider describes it as analytics-only and explicitly not financial, legal or investment advice. Four operations over OpenAPI 3.0, bearer authenticated, with a free tier and an x402 machine-payment surface on Base.

54ch10 publishes 1 API on the APIs.io network: Brief API. Tagged areas include Security, Risk, Wallets, Phishing, and Blockchain.

54ch10’s developer surface includes documentation and 2 more developer resources.

15.8/100 emerging Agent 16/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
1 APIs
SecurityRiskWalletsPhishingBlockchainAgentsx402Machine Payments

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 15.8/100 · emerging
Contract Quality 10.4 / 21
Developer Ergonomics 1.6 / 17
Access Clarity 0.0 / 17
Operational Transparency 0.0 / 11
Contract Governance 0.0 / 10
Discoverability 5.5 / 9
Regulatory Posture 0.0 / 15
Agent readiness — 16/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 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 0 / 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 Surface 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Payments 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.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/54ch10: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

54ch10 Brief API

Pre-interact risk briefs for addresses, tokens and URLs. GET /v1/brief and a free tier at /v1/brief/free, plus /health and an x402 discovery document. Bearer authenticated.

Resources

Documentation 1

Reference material describing how the API behaves

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: 54ch10
name: 54ch10
description: '54ch10 serves pre-interact risk briefs for wallet addresses, tokens and URLs — phishing, scam, honeypot and
  URL-reputation heuristics an agent can call BEFORE it signs, approves, bridges or opens a dapp URL. A brief returns a 0–100
  score where higher is more concerning, a band, flags, a summary and the sources behind it, so a caller can gate its next
  tool call on policy: refuse on critical, require human confirmation on elevated. The provider describes it as analytics-only
  and explicitly not financial, legal or investment advice. Four operations over OpenAPI 3.0, bearer authenticated, with a
  free tier and an x402 machine-payment surface on Base.'
type: Index
url: https://raw.githubusercontent.com/api-evangelist/54ch10/refs/heads/main/apis.yml
created: '2026-08-24'
modified: '2026-08-24'
specificationVersion: '0.23'
tags:
- Security
- Risk
- Wallets
- Phishing
- Blockchain
- Agents
- x402
- Machine Payments
tags_raw:
- wallet risk
- phishing
- scam detection
- url reputation
- x402
apis:
- aid: 54ch10:54ch10-brief-api
  name: 54ch10 Brief API
  description: Pre-interact risk briefs for addresses, tokens and URLs. GET /v1/brief and a free tier at /v1/brief/free, plus
    /health and an x402 discovery document. Bearer authenticated.
  humanURL: https://54ch10.uk/AGENT.md
  baseURL: https://54ch10.uk
  tags:
  - Security
  - Risk
  - Wallets
  properties:
  - type: OpenAPI
    url: openapi/54ch10-brief-api-openapi.yml
  - type: APIReference
    url: https://54ch10.uk/openapi.json
  - type: Documentation
    url: authentication/54ch10-agent.md
  - type: FinOps
    url: finops/54ch10-x402-manifest.json
common:
- type: Website
  url: https://54ch10.uk/
- type: FinOps
  url: finops/54ch10-x402-manifest.json
- type: Documentation
  url: authentication/54ch10-agent.md
maintainers:
- FN: 54ch10
  email: 54ch10.brief@gmail.com
  url: https://54ch10.uk/
x-provenance:
  added: '2026-08-24'
  method: searched
  source: https://54ch10.uk/openapi.json
  note: 'Submitted via apis.io/add on 2026-08-24 and auto-published by the gate at rating 37. The submitted APIs.json at https://54ch10.uk/apis.json
    returns 404 against a control that also 404s with an identical 531-byte JSON body, so the 404 is real — a bad pointer
    in the submission, not an absent surface. There is no llms.txt either. What IS served was fetched and confirmed: OpenAPI
    3.0.3 at /openapi.json (4 paths, bearer auth, though zero component schemas), an AGENT.md written directly at agents rather
    than at humans, and an x402 discovery document at /.well-known/x402 declaring x402Version 2 on the Base network with the
    payai facilitator. /health returns 200 JSON. Both brief endpoints return 400 JSON on a malformed call, which is validation
    rather than a stub. The AGENT.md is the interesting artifact: it tells a calling agent the order of operations — resolve
    the target, GET /v1/brief, then gate the next tool call on the returned band — and tells operators to log cached_at and
    sources[].status so they can tell a stub signal from a live one. It is kept here in full. Note the brand: the provider
    states it is "54ch10", NOT "SACHIO".'

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/54ch10"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/54ch10/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/54ch10/evidence"

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

Get an API key

Free tier, no email required.

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