Hamsa

Hamsa (formerly HamsaPay) is a San Francisco-based financial infrastructure company "powering the Finternet." It builds the Hamsa Unified Confidential Ledger (UCL), a privacy-enabled, EVM-compatible, permissioned Layer-2 blockchain for banks and financial institutions, plus the Hamsa Privacy module that uses zero-knowledge-proof (ZKP) rollups on Hyperledger Besu to run confidential Delivery-versus-Payment (DvP) and Payment-versus-Payment (PvP) settlement, tokenized deposits, stablecoins, and CBDCs. The developer platform exposes an EVM-standard JSON-RPC API (eth_* methods) and DvP escrow smart contracts, authenticated with Ethereum message signatures and role-based access control. Hamsa has tokenized over $3.2B for Tier-1/Tier-2 banks (including Banco Safra's Safra Dolar stablecoin) and participates in the Brazilian Drex CBDC pilot.

Hamsa is profiled on the APIs.io network. Tagged areas include Company, Financial Services, Blockchain, Payments, and Tokenization.

Hamsa’s developer surface includes documentation, API reference, engineering blog, authentication, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

20.8/100 emerging ▬ flat Agent 3/100 human only Front door AI 3/6 light saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs

Company Financial Services Blockchain Payments Tokenization Privacy Zero-Knowledge ProofsCBDCSettlement DeFi EVM JSON-RPC

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 20.8/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 6.1 / 17

Access Clarity 4.7 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.7 / 9

Regulatory Posture 3.3 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/hamsa/"><img src="https://apis.io/badge/hamsa/card.svg" alt="Hamsa on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 27.6 — up to +14.5 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/hamsa/apis.yml: open an issue on github.com/api-evangelist/hamsa to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Stablecoins and Tokenization (stablecoin issuers, tokenized assets)	undeclared	-	-	-
LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

JSON RPC

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hamsa Authentication

signature · 1 scheme

SECURITY

Hamsa Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Conformance

Conformance

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Twitter

Twitter

Source (apis.yml)

aid: hamsa
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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/hamsa.png
name: Hamsa
description: Hamsa (formerly HamsaPay) is a San Francisco-based financial infrastructure company "powering the Finternet."
  It builds the Hamsa Unified Confidential Ledger (UCL), a privacy-enabled, EVM-compatible, permissioned Layer-2 blockchain
  for banks and financial institutions, plus the Hamsa Privacy module that uses zero-knowledge-proof (ZKP) rollups on Hyperledger
  Besu to run confidential Delivery-versus-Payment (DvP) and Payment-versus-Payment (PvP) settlement, tokenized deposits,
  stablecoins, and CBDCs. The developer platform exposes an EVM-standard JSON-RPC API (eth_* methods) and DvP escrow smart
  contracts, authenticated with Ethereum message signatures and role-based access control. Hamsa has tokenized over $3.2B
  for Tier-1/Tier-2 banks (including Banco Safra's Safra Dolar stablecoin) and participates in the Brazilian Drex CBDC pilot.
url: https://raw.githubusercontent.com/api-evangelist/hamsa/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Company
- Financial Services
- Blockchain
- Payments
- Tokenization
- Privacy
- Zero-Knowledge Proofs
- CBDC
- Settlement
- DeFi
- EVM
- JSON-RPC
tags_raw:
- Company
- Financial Services
- Blockchain
- Payments
- Tokenization
- Privacy
- Zero-Knowledge Proofs
- CBDC
- Settlement
- DeFi
- EVM
- JSON-RPC
- Financial-Services
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.hamsa.com
- type: DeveloperPortal
  url: https://developer.hamsa.com/
- type: Documentation
  url: https://developer.hamsa.com/docs/hamsa-privacy-overview
- type: APIReference
  url: https://developer.hamsa.com/reference/api-documentation
- type: Login
  url: https://developer.hamsa.com/login
- type: Blog
  url: https://www.hamsa.com/newsroom
- type: TermsOfService
  url: https://www.hamsa.com/legal/terms-of-use
- type: PrivacyPolicy
  url: https://www.hamsa.com/legal/privacy-policy
- type: LinkedIn
  url: https://www.linkedin.com/company/hamsa-finance
- type: Twitter
  url: https://x.com/hamsafinance
- type: LLMsTxt
  url: llms/hamsa-llms.txt
- type: Authentication
  url: authentication/hamsa-authentication.yml
- type: Conventions
  url: conventions/hamsa-conventions.yml
- type: Conformance
  url: conformance/hamsa-conformance.yml
- type: DomainSecurity
  url: security/hamsa-domain-security.yml
- type: WellKnown
  url: well-known/hamsa-well-known.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Hamsa API — frequently asked questions

How do I authenticate with the Hamsa API?

Hamsa uses bearer-token authentication (signature · 1 scheme). The details are profiled on APIs.io as Hamsa Authentication.

Is the Hamsa API ready for AI agents?

Hamsa has a Kin Score of 20.8 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.

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/hamsa"

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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