AiFinPay
AiFinPay provides economic infrastructure for autonomous AI agents, offering non-custodial wallets, paid access to websites, APIs and MCP tools via HTTP 402, and AI‑traffic monetization for merchants. It enables agents to pay for resources and merchants to monetize AI‑driven traffic, supporting multiple blockchain networks and a developer ecosystem with SDKs and documentation.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles AiFinPay the way a machine reads it — 52 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — AiFinPay scores 44.9/100 (developing), with a separate agent-readiness read of 40/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-11-06 · rubric v0.27.0
Put this on your own site. The badge is drawn live from AiFinPay's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aifinpay-io/"
title="AiFinPay on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aifinpay-io.svg"
alt="AiFinPay Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/aifinpay-io/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aifinpay-io/"
title="AiFinPay on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aifinpay-io/card.svg"
alt="AiFinPay Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile AiFinPay
Each block below is one kind of artifact we hold for AiFinPay. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 36
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
AiFinPay Admin API
admin-api router — see backend/routes/admin-api.js
AiFinPay Admin API
admin router — see backend/routes/admin.js
AiFinPay Admin Views API
admin-views router — see backend/routes/admin-views.js
AiFinPay Agent Public API
agent-public router — see backend/routes/agent-public.js
AiFinPay Agent Transactions API
agent-transactions router — see backend/routes/agent-transactions.js
AiFinPay Agents API
agents router — see backend/routes/agents.js
AiFinPay Aifp API
aifp router — see backend/routes/aifp.js
AiFinPay B2b API
b2b router — see backend/routes/b2b.js
AiFinPay Cross Chain API
cross-chain router — see backend/routes/cross-chain.js
AiFinPay Dashboard API
dashboard router — see backend/routes/dashboard.js
AiFinPay Discovery API
discovery router — see backend/routes/discovery.js
AiFinPay Dns Control API
dns-control router — see backend/routes/dns-control.js
AiFinPay Founding Offer API
founding-offer router — see backend/routes/founding-offer.js
AiFinPay Health API
health router — see backend/routes/health.js
AiFinPay Internal API
internal router — see backend/routes/internal.js
AiFinPay Invoices API
invoices router — see backend/routes/invoices.js
AiFinPay Me Agents API
me-agents router — see backend/routes/me-agents.js
AiFinPay Me Auth API
me-auth router — see backend/routes/me-auth.js
AiFinPay Me Merchants API
me-merchants router — see backend/routes/me-merchants.js
AiFinPay Merchant Config API
merchant-config router — see backend/routes/merchant-config.js
AiFinPay Network Agents API
network-agents router — see backend/routes/network-agents.js
AiFinPay Network Stats API
network-stats router — see backend/routes/network-stats.js
AiFinPay OAuth API
oauth router — see backend/routes/oauth.js
AiFinPay Partner Agents API
partner-agents router — see backend/routes/partner-agents.js
AiFinPay Partner Applications API
partner-applications router — see backend/routes/partner-applications.js
AiFinPay Partner Auth API
partner-auth router — see backend/routes/partner-auth.js
AiFinPay Partners API
partners router — see backend/routes/partners.js
AiFinPay Passport API
passport router — see backend/routes/passport.js
AiFinPay Protocol API
protocol router — see backend/routes/protocol.js
AiFinPay Providers API
providers router — see backend/routes/providers.js
AiFinPay Reporting API
reporting router — see backend/routes/reporting.js
AiFinPay Seats API
seats router — see backend/routes/seats.js
AiFinPay Settlement API
settlement router — see backend/routes/settlement.js
AiFinPay Site Check API
site-check router — see backend/routes/site-check.js
AiFinPay Telemetry API
telemetry router — see backend/routes/telemetry.js
AiFinPay Webhooks API
webhooks router — see backend/routes/webhooks.js
Scroll within the panel for all 36 ·
Agent Skills 4
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
aifinpay-io-create-and-configure-merchant
AGENT SKILLaifinpay-io-create-merchant-with-resource
AGENT SKILLaifinpay-io-manage-webhook
AGENT SKILLaifinpay-io-settlement-create-invoice
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Aifinpay Io Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
AiFinPay API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
MerchantConfigCommitted
JSON SCHEMAMerchantConfigExport
JSON SCHEMAMerchantConfigImport
JSON SCHEMAMerchantConfigPreview
JSON SCHEMAMerchantConfigView
JSON SCHEMAMerchantSiteBatchPreview
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for AiFinPay — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aifinpay-io · machine-readable index on apis.io
This is an independent, third-party profile of AiFinPay, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.