Yapily

Drive the product through a documented public API G

Agent access

Connect an agent via an official MCP server G

Agent access

Plug MCP servers into this product so it can use their tools G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Point an agent at llms.txt or agent-oriented docs G

Agent access

Subscribe to events via webhooks G

Agent access

Build against official SDKs G

Agent access

Run the product headlessly / in CI for automation G

Agent access

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Set up automations that run autonomously in the background G

Agentic features

Explore an interactive API reference with runnable examples G

Api quality

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Operate the product with natural-language commands G

Agentic features

Issue scoped/least-privilege API credentials for an agent G

Agent access

Rely on versioned APIs with a documented deprecation policy G

Api quality

Use an official CLI G

Agent access

Test against a sandbox environment without touching production data G

Api quality

Fetch a real-time balance for a connected account before initiating a payment — a documented balance endpoint intended for NSF and risk checks C

Balances

Let a user connect their bank with a drop-in hosted flow — create a session server-side, open the widget, and get back a token for the connected account — without building institution UI myself C

Hosted flows

A sandbox with test institutions and documented test credentials lets me exercise linking, data retrieval, and error states end-to-end before touching a real bank account C

Sandbox

An agent can operate the platform — create link sessions, retrieve balances and transactions, and manage connections through the API or an MCP surface with scoped credentials C

Agent operations

Pull transaction history for a connected account through the API — paginated, with documented history depth and a sync pattern for fetching only what changed C

Transactions

Define rules that trigger actions automatically on events G

Export all of my data in open formats and leave G

Obtain verified account and routing numbers (or tokenized equivalents) from a linked account to fund ACH or bank-debit payments without micro-deposits C

Ach details

Prevent my data from being used to train AI models G

Self-host the core product G

The platform documents how many institutions it reaches and where — published coverage numbers and geographies I can check against where my users actually bank C

Coverage

Recurring bank payments are supported — variable recurring payments, standing consents, or documented recurring debit flows built on the connection C

Recurring

Retrieve account-holder details — names, addresses, contact data on file at the bank — to match the account owner against my customer C

Ownership

Data changes arrive as signed webhooks — new transactions, balance updates, connection state changes — so my system stays current without polling C

Webhooks

Do everything through the API that I can do in the UI G

Initiate a bank payment from a connected account — a documented pay-by-bank or payment-initiation product with its live geographies stated honestly C

Pay by bank

One link session can power multiple data products — auth, balances, transactions, identity — without forcing the user through separate connection flows per product C

Multi product

Raw bank transactions come back enriched — cleaned merchant names, categories, and logos — documented as a capability of the platform, not left as an exercise for me C

Enrichment

I request only the data scopes I need — product-scoped consents and documented data-minimization controls, not an all-or-nothing grant C

Scopes

Schedule recurring jobs or workflows G

The data comes back agent-consumable — clean structured JSON, documented schemas, and enrichment an automated financial workflow can reason over without heuristic parsing C

Agent data

Connections to major institutions use bank-hosted OAuth rather than screen-scraped credentials — the platform documents its OAuth coverage and how legacy credential flows are being retired C

Oauth

Go from signup to my first linked sandbox account fast — self-serve API keys, a runnable quickstart, and client libraries in my language C

Quickstart

Perform bulk operations across many items at once G

Per-institution health is visible — documented institution statuses, outage or degradation signals, and error codes that distinguish a bank problem from my problem C

Status

Trigger an on-demand refresh of a connected account's data through the API when my use case needs now-fresh data, with the refresh semantics documented C

Refresh

Broken connections are repairable — expired or revoked links surface as documented statuses, and users can re-authenticate in an update flow without starting over C

Repair

Choose where my data is stored (region/residency) G

Control data retention and deletion G

End users can see and revoke what they've shared — a documented consent surface or portal where a user manages which apps hold access to their bank data C

Consent

Linked accounts plug into my payment processor — documented integrations or token exchange that hand verified account credentials to third-party processors and platforms C

Processor tokens

Opt out of telemetry and usage tracking G

Read the product's source under an open license G

Sever and clean up — a documented way to delete a connection or user and have the platform stop collecting and purge held data C

Deletion

The platform derives income and cash-flow signals from connected accounts — recurring streams, payroll detection, or documented income verification products built on the same data C

Cashflow

Version, review, and roll back my automations G