Hamsa website screenshot

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.

26.0/100 emerging ▬ flat Agent 14/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
0 APIs
CompanyFinancial ServicesBlockchainPaymentsTokenizationPrivacyZero-Knowledge ProofsCBDCSettlementDeFiEVMJSON-RPC

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 26.0/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 7.4 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 14/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/hamsa: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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

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

Source (apis.yml)

apis.yml Raw ↑
aid: hamsa
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  generated: '2026-07-22'
  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.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Financial Services
- Blockchain
- Payments
- Tokenization
- Privacy
- Zero-Knowledge Proofs
- CBDC
- Settlement
- DeFi
- EVM
- JSON-RPC
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