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.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Hamsa the way a machine reads it — 2 machine-readable artifacts, 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 — Hamsa scores 26.0/100 (emerging), with a separate agent-readiness read of 14/100 (human only). 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 Hamsa
Each block below is one kind of artifact we hold for Hamsa. 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.
Security 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.
Resources
Every other property we hold for Hamsa — 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 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hamsa · machine-readable index on apis.io