Breeze
Breeze is instant, non-custodial yield infrastructure for Solana. Any Solana app — wallets, payment products, trading platforms, Telegram bots, and AI agents — can embed automated yield for its users with a few lines of code via the Breeze REST API, a TypeScript SDK, prebuilt UI components, and an Agent Kit (MCP server, x402 and MPP pay-per-call access, and a drop-in Agent Skill). Yield is generated on USDC, USDT, USDS, SOL and Solana LSTs (JitoSOL, mSOL, JupSOL) plus JLP while custody stays with the user and positions remain liquid and composable. Breeze was built by Anagram and is backed by Multicoin Capital.
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 Breeze the way a machine reads it — 19 machine-readable artifacts across 15 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 — Breeze scores 39.0/100 (thin), with a separate agent-readiness read of 65/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Breeze
Each block below is one kind of artifact we hold for Breeze. 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 15
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.
Breeze Admin API
Administrative operations
Breeze Deposits API
Deposit operations
Breeze fund API
The fund API from Breeze — 1 operation(s) for fund.
Breeze Funds API
Fund management operations
Breeze Global Config API
Global configuration and supported assets
Breeze Organization API Keys API
Organization API key management
Breeze Organization API
Organization onboarding and status
Breeze Organization Funds API
The Organization Funds API from Breeze — 1 operation(s) for organization funds.
Breeze Organization Settings API
The Organization Settings API from Breeze — 1 operation(s) for organization settings.
Breeze Selective Yield Sources API
The Selective Yield Sources API from Breeze — 1 operation(s) for selective yield sources.
Breeze Strategies API
The Strategies API from Breeze — 14 operation(s) for strategies.
Breeze Strategy API
The Strategy API from Breeze — 1 operation(s) for strategy.
Breeze User Data API
User balance and yield data
Breeze Withdrawals API
Withdrawal operations
Breeze Yield Sources API
Yield source information and statistics
Scroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
breeze-mcp.yml
MCP SERVERSecurity 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 Breeze — 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 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
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
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/breeze · machine-readable index on apis.io