Frax Finance
Frax Finance is a fractional-algorithmic stablecoin protocol offering FRAX (USD-pegged stablecoin), FPI (Frax Price Index stablecoin pegged to a consumer goods basket), frxETH (liquid ETH staking derivative), and supporting DeFi infrastructure including Fraxswap, Fraxlend, and Fraxtal L2. The protocol operates Algorithmic Market Operations (AMOs) to manage collateral and generate revenue, and exposes public REST APIs for querying token supply, collateral ratios, AMO positions, pool APRs, and frxETH staking analytics.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Frax Finance the way a machine reads it — 23 machine-readable artifacts across 17 APIs, 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 — Frax Finance scores 35.2/100 (thin), with a separate agent-readiness read of 39/100 (agent aware). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Frax Finance
Each block below is one kind of artifact we hold for Frax Finance. 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 17
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.
Frax Finance v1-gauge API
The v1-gauge API from Frax Finance — 2 operation(s) for v1-gauge.
Frax Finance v1-prices API
The v1-prices API from Frax Finance — 7 operation(s) for v1-prices.
Frax Finance v1-protocol API
The v1-protocol API from Frax Finance — 4 operation(s) for v1-protocol.
Frax Finance v1-staking API
The v1-staking API from Frax Finance — 6 operation(s) for v1-staking.
Frax Finance v1-vefpis API
The v1-vefpis API from Frax Finance — 2 operation(s) for v1-vefpis.
Frax Finance v1-vefxs API
The v1-vefxs API from Frax Finance — 2 operation(s) for v1-vefxs.
Frax Finance v2-fpifpis API
The v2-fpifpis API from Frax Finance — 7 operation(s) for v2-fpifpis.
Frax Finance v2-frax API
The v2-frax API from Frax Finance — 6 operation(s) for v2-frax.
Frax Finance v2-fraxferry API
The v2-fraxferry API from Frax Finance — 7 operation(s) for v2-fraxferry.
Frax Finance v2-fraxswap API
The v2-fraxswap API from Frax Finance — 12 operation(s) for v2-fraxswap.
Frax Finance v2-frxeth API
The v2-frxeth API from Frax Finance — 12 operation(s) for v2-frxeth.
Frax Finance v2-frxusd API
The v2-frxusd API from Frax Finance — 4 operation(s) for v2-frxusd.
Frax Finance v2-fxb API
The v2-fxb API from Frax Finance — 6 operation(s) for v2-fxb.
Frax Finance v2-gauges API
The v2-gauges API from Frax Finance — 8 operation(s) for v2-gauges.
Frax Finance v2-gov API
The v2-gov API from Frax Finance — 5 operation(s) for v2-gov.
Frax Finance v2-lfrax API
The v2-lfrax API from Frax Finance — 2 operation(s) for v2-lfrax.
Frax Finance v2-sfrxusd API
The v2-sfrxusd API from Frax Finance — 4 operation(s) for v2-sfrxusd.
Scroll within the panel for all 17 ·
Pricing 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Finops
FINOPSSemantic 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.
Frax Finance Context
JSON-LDSecurity Posture 1
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 Frax Finance — 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.
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
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/frax · machine-readable index on apis.io