Jiko

Jiko is a fintech infrastructure company that turns idle cash into US Treasury bills held in the customer's own name, combining a nationally chartered bank, a registered broker-dealer, and a real-time settlement network (JikoNet) behind a single API. Its "Jiko as a Service" platform lets partners embed T-bill-backed accounts, virtual and physical debit cards, pockets (paired bank + brokerage accounts), and multi-rail money movement (ACH, wire, SWIFT, cards, and 24/7 on-us JikoNet transfers) into their own applications. Jiko exposes two OAuth 2.0 / HMAC-secured REST APIs — a Customer API for direct integrators and a Partner API for embedding Jiko products on behalf of end customers.

Jiko publishes 2 APIs on the APIs.io network. Tagged areas include Company, Banking, Payments, Treasury, and Embedded Finance.

The Jiko catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Jiko’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, signup flow, developer portal, and 23 more developer resources.

🌐 Visit website 📡 Source on GitHub

55.1/100 strong ▬ flat Agent 35/100 agent ready saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0

AccessSelf serve

2 APIs

Company Banking Payments Treasury Embedded Finance Fintech Cards Settlement Broker-Dealer Banking as a Service

Kin Score

Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0

Composite quality — 55.1/100 · strong

Contract Quality 8.8 / 21

Developer Ergonomics 11.2 / 17

Access Clarity 8.5 / 17

Operational Transparency 6.1 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 9.4 / 15

Agent readiness — 35/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/jiko: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Jiko Customer API

The Customer API is for Jiko customers integrating Jiko directly into their own internal systems. It uses OAuth 2.0 (authorization code and client credentials flows) with Privat...

Jiko Partner API

The Partner API is for applications that embed Jiko's services and offer Jiko products to their own customers. It authenticates with a bearer token obtained via Login, and requi...

Rate Limits 1

Documented rate limits and quota policies.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Jiko Scopes

25 scopes · authorizationCode/clientCredentials

25 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Portal

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

Lifecycle

Webhooks

Conformance

DataModel

Access & Security 6

Authentication, authorization, and security posture

TrustCenter

Compliance

Authentication

OAuthScopes

TrustCenter

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: jiko
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/jiko.png
name: Jiko
description: Jiko is a fintech infrastructure company that turns idle cash into US Treasury bills held in the customer's own
  name, combining a nationally chartered bank, a registered broker-dealer, and a real-time settlement network (JikoNet) behind
  a single API. Its "Jiko as a Service" platform lets partners embed T-bill-backed accounts, virtual and physical debit cards,
  pockets (paired bank + brokerage accounts), and multi-rail money movement (ACH, wire, SWIFT, cards, and 24/7 on-us JikoNet
  transfers) into their own applications. Jiko exposes two OAuth 2.0 / HMAC-secured REST APIs — a Customer API for direct
  integrators and a Partner API for embedding Jiko products on behalf of end customers.
url: https://raw.githubusercontent.com/api-evangelist/jiko/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: enriched
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Banking
- Payments
- Treasury
- Embedded Finance
- Fintech
- Cards
- Settlement
- Broker-Dealer
- Banking as a Service
apis:
- aid: jiko:jiko-customer-api
  name: Jiko Customer API
  humanURL: https://docs.jiko.io/products/customer-api
  baseURL: https://api.sandbox-api.jikoservices.com/api/v1
  description: The Customer API is for Jiko customers integrating Jiko directly into their own internal systems. It uses OAuth
    2.0 (authorization code and client credentials flows) with Private Key JWT client authentication, PKCE (required) and
    DPoP (optional), and covers pockets, portals, transfers (JikoNet, wires, SWIFT, ACH), counterparties, trades and trading
    strategies, transactions, reports, teams, subscriptions/webhooks, and customer management.
  tags:
  - Banking
  - Treasury
  - Payments
  - Transfers
  - Authentication
  tags_raw:
  - Banking
  - Treasury
  - Payments
  - Transfers
  - OAuth
  properties:
  - type: Documentation
    url: https://docs.jiko.io/products/customer-api
  - type: APIReference
    url: https://docs.jiko.io/products/customer-api
  - type: GettingStarted
    url: https://docs.jiko.io/products/customer-api/guides/oauth/getting-started
  - type: Authentication
    url: authentication/jiko-authentication.yml
  - type: OAuthScopes
    url: scopes/jiko-scopes.yml
  - type: Webhooks
    url: asyncapi/jiko-webhooks.yml
  - type: ChangeLog
    url: https://docs.jiko.io/products/customer-api/changelog
- aid: jiko:jiko-partner-api
  name: Jiko Partner API
  humanURL: https://docs.jiko.io/products/partner-api
  baseURL: https://api.sandbox-api.jikoservices.com/api/v1
  description: The Partner API is for applications that embed Jiko's services and offer Jiko products to their own customers.
    It authenticates with a bearer token obtained via Login, and requires an x-jiko-idempotency header plus an HMAC-SHA256
    x-jiko-signature request signature and IP allowlisting. It covers partner-tenant onboarding (KYC/KYB), customers, pockets,
    portals, cards (physical and virtual), ACH originations, wires, JikoNet transfers, and event subscriptions/webhooks.
  tags:
  - Banking
  - Embedded Finance
  - Cards
  - Onboarding
  - Webhook
  tags_raw:
  - Banking
  - Embedded Finance
  - Cards
  - Onboarding
  - Webhooks
  properties:
  - type: Documentation
    url: https://docs.jiko.io/products/partner-api
  - type: APIReference
    url: https://docs.jiko.io/products/partner-api
  - type: Authentication
    url: authentication/jiko-authentication.yml
  - type: Webhooks
    url: asyncapi/jiko-webhooks.yml
  - type: ChangeLog
    url: https://docs.jiko.io/products/partner-api/changelog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://jiko.com
- type: DeveloperPortal
  url: https://docs.jiko.io
- type: Documentation
  url: https://docs.jiko.io
- type: APIReference
  url: https://docs.jiko.io/products/customer-api
- type: GettingStarted
  url: https://docs.jiko.io/products/customer-api/guides/oauth/getting-started
- type: Blog
  url: https://jiko.com/blog
- type: Support
  url: https://jiko.com
- type: SignUp
  url: https://authentication-portal.sandbox-api.jikoservices.com/sign-up
- type: Portal
  url: https://business.jiko.io
- type: TermsOfService
  url: https://jiko.com/agreements-disclosures
- type: PrivacyPolicy
  url: https://jiko.com/privacy-policy
- type: TrustCenter
  url: https://jiko.com/trust-and-safety
- type: Compliance
  url: https://jiko.com/trust-and-safety
- type: Authentication
  url: authentication/jiko-authentication.yml
- type: OAuthScopes
  url: scopes/jiko-scopes.yml
- type: Conventions
  url: conventions/jiko-conventions.yml
- type: Idempotency
  url: conventions/jiko-conventions.yml
- type: RateLimits
  url: rate-limits/jiko-rate-limits.yml
- type: ChangeLog
  url: changelog/jiko-changelog.yml
- type: Sandbox
  url: sandbox/jiko-sandbox.yml
- type: Lifecycle
  url: lifecycle/jiko-lifecycle.yml
- type: Webhooks
  url: asyncapi/jiko-webhooks.yml
- type: WellKnown
  url: well-known/jiko-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/jiko-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  name: Jiko MCP Server (candidate)
- type: LLMsTxt
  url: llms/jiko-llms.txt
- type: Conformance
  url: conformance/jiko-conformance.yml
- type: TrustCenter
  url: security/jiko-trust-center.yml
- type: DomainSecurity
  url: security/jiko-domain-security.yml
- type: DataModel
  url: data-model/jiko-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
  name: Jiko Agent Skills
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/jiko"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/jiko/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/jiko/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.