Akoya
Akoya operates a tokenized, consumer-permissioned data-access network for US open finance, reaching 4,500+ financial institutions and powering 7,500+ apps and data recipients. It implements the Financial Data Exchange (FDX) API standard to replace screen-scraping with token-permissioned, OAuth 2.0 access to consumer financial data. The Akoya API surface is a 100% API-driven catalog organized into consumer data-access products — Accounts, Balances, Transactions, Investments (holdings and tax lots), Statements, Customers, Tax forms, and Payments (ACH/RTP payment networks) — plus a set of platform/service APIs for Consent, Apps Management, and Notifications. Consumers authenticate at their own financial institution's authorization server; data recipients exchange authorization codes for access tokens and call FDX-aligned REST endpoints. Documentation is published as OpenAPI 3.1.0 (rendered via the docs.akoya.com reference hub); Akoya's GitHub org ships Go code samples for the OAuth client-credentials, auth-code, and account-fetch flows. There is no publicly downloadable OpenAPI/Postman artifact — production access requires a network membership agreement.
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 Akoya the way a machine reads it — 18 machine-readable artifacts across 11 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 — Akoya scores 55.0/100 (developing), with a separate agent-readiness read of 30/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 Akoya
Each block below is one kind of artifact we hold for Akoya. 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 11
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.
Akoya Accounts API
FDX-aligned REST endpoints returning the list of a consumer's permissioned accounts and detailed account information (account identifiers, type, status, nickname, and product de...
Akoya Balances API
Returns real-time and available balance information for a consumer's permissioned accounts across the Akoya network. Balances are exposed as FDX-aligned fields and are commonly ...
Akoya Transactions API
Retrieves transaction history for a consumer's permissioned accounts, returning FDX-aligned transaction records (amount, date, description, categorization, and status). Supports...
Akoya Investments API
Provides FDX-aligned investment and brokerage account data for consumer-permissioned accounts, including holdings/positions and tax lots for wealth-management and investing use ...
Akoya Statements API
Lists and retrieves account statements for a consumer's consented accounts, returning the set of available statements (period, type, and document reference) so recipients can ac...
Akoya Customers API
Returns FDX-aligned customer/party information for the consumer who owns the permissioned accounts — name, contact details, and identity attributes — supporting identity verific...
Akoya Payments API
Provides secure, consumer-permissioned access to ACH and real-time payment (RTP) account credentials — tokenized account and routing identifiers (bankId, identifier, type, ident...
Akoya Tax API
Retrieves FDX-aligned tax documents for a consumer's permissioned accounts — 1099 form variants (1099-INT, 1099-DIV, 1099-B, and related) and associated tax data — so recipients...
Akoya Consent API
Platform/service API for managing consumer consent grants across the Akoya network, letting data recipients look up and manage the consent records that authorize access to a con...
Akoya Apps Management API
Platform/service API for creating and managing a data recipient's applications on the Akoya network — registering apps, managing client credentials and configuration, and admini...
Akoya Notifications API
Platform/service API for subscribing to and receiving operational notifications about the Akoya network, such as data-provider outages and availability events, delivered via web...
Scroll within the panel for all 11 ·
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.
Akoya Plans Pricing
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.
Akoya 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.
Akoya Finops
FINOPSEvent 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.
Akoya Notifications Webhooks
ASYNCAPISecurity Posture 3
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.
Resources
Every other property we hold for Akoya — 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 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
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/akoya · machine-readable index on apis.io