TreasurySpring
TreasurySpring is a digital platform for institutional cash management that helps organisations holding large excess cash balances minimise risk, maximise return and optimise time by diversifying across secure counterparties via standardised Fixed Term Funds (FTFs). Its Public API (OpenAPI 3.1) gives an authorised user programmatic access to their entities, fund cells, obligor exposures, indications, subscriptions, holdings, tasks and a normalised event stream — the full FTF lifecycle from subscription to live holding — with OAuth 2.0 auth, offset and cursor pagination, webhooks, and a published, read-only Model Context Protocol (MCP) server for AI agents.
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 TreasurySpring the way a machine reads it — 18 machine-readable artifacts across 13 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 — TreasurySpring scores 50.7/100 (developing), with a separate agent-readiness read of 75/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.
How we profile TreasurySpring
Each block below is one kind of artifact we hold for TreasurySpring. 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 13
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.
TreasurySpring Calendar API
Get Calendar information
TreasurySpring Cells API
Get information about Cells
TreasurySpring Entities API
Get information about Entities
TreasurySpring Event Checkpoints API
Server-managed cursors for stateless event stream consumers. In most cases, checkpoints are not needed. If your system can persist data locally (e.g. in a database, file, or key...
TreasurySpring Events API
Stream of normalised events for integration and reconciliation
TreasurySpring Healthcheck API
Check the status of the API
TreasurySpring Holdings API
Get information about holdings. For how subscriptions become holdings and how holdings move through their lifecycle, see the FTF Lifecycle section.
TreasurySpring Indications API
Get information about Indications
TreasurySpring OAuth API
OAuth 2.0 endpoint to exchange your Client Credentials for a token. This token can then be used to access the API.
TreasurySpring Obligor Exposure API
Get information about Obligors
TreasurySpring Subscriptions API
FTF Subscriptions
TreasurySpring Tasks API
Get information about Pending Tasks
TreasurySpring Webhooks API
Integrate with webhooks to receive notifications
Scroll within the panel for all 13 ·
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.
treasuryspring-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Treasuryspring Events Webhooks
ASYNCAPISecurity 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 TreasurySpring — 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 5
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
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/treasuryspring · machine-readable index on apis.io