PolySign
PolySign, Inc. is an Oakland / San Francisco / New York financial technology company building blockchain-enabled infrastructure for institutional digital asset capital markets and payments. Founded by Arthur Britto, David Schwartz and Jack McDonald, PolySign operates a third-generation permissioned blockchain and the AtomicNet settlement network, and was the parent of Standard Custody & Trust Company, the NYDFS-regulated digital asset custody, trading and settlement platform acquired by Ripple in 2024. PolySign publishes three OpenAPI 3.0.3 contracts for AtomicNet — the AtomicNet API Server (node interface for assets, orders, escrow and beneficiary authorizations, settlements, settlement confirmations, book transfers, partners and investors), the AtomicNet Merchant Gate Node, and the AtomicNet ABC Proxy Service (account registration, digest memorialization, signing and testnet faucet) — all authenticated with OAuth 2.0 client credentials issued by a PolySign-hosted token endpoint.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles PolySign the way a machine reads it — 39 machine-readable artifacts across 17 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 — PolySign scores 30.5/100 (thin), with a separate agent-readiness read of 36/100 (agent ready). 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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from PolySign's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/polysign/"
title="PolySign on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/polysign.svg"
alt="PolySign Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/polysign/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/polysign/"
title="PolySign on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/polysign/card.svg"
alt="PolySign Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile PolySign
Each block below is one kind of artifact we hold for PolySign. 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 17
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.
PolySign ABC Accounts API
The ABC Accounts API from PolySign — 3 operation(s) for abc accounts.
PolySign ABC Memorials API
The ABC Memorials API from PolySign — 2 operation(s) for abc memorials.
PolySign ABC Signing API
The ABC Signing API from PolySign — 1 operation(s) for abc signing.
PolySign ABC Testnet API
The ABC Testnet API from PolySign — 2 operation(s) for abc testnet.
PolySign Asset API
The asset API from PolySign — 5 operation(s) for asset.
PolySign Authentication API
The authentication API from PolySign — 1 operation(s) for authentication.
PolySign beneficiary authorization API
The beneficiary authorization API from PolySign — 6 operation(s) for beneficiary authorization.
PolySign book transfer API
The book transfer API from PolySign — 5 operation(s) for book transfer.
PolySign book transfer confirmation API
The book transfer confirmation API from PolySign — 4 operation(s) for book transfer confirmation.
PolySign escrow authorization API
The escrow authorization API from PolySign — 6 operation(s) for escrow authorization.
PolySign Investor API
The investor API from PolySign — 2 operation(s) for investor.
PolySign Order API
The order API from PolySign — 5 operation(s) for order.
PolySign Partner API
The partner API from PolySign — 3 operation(s) for partner.
PolySign Settlement API
The settlement API from PolySign — 5 operation(s) for settlement.
PolySign settlement confirmation API
The settlement confirmation API from PolySign — 6 operation(s) for settlement confirmation.
PolySign System API
The system API from PolySign — 4 operation(s) for system.
PolySign Utility API
The utility API from PolySign — 5 operation(s) for utility.
Scroll within the panel for all 17 ·
Open Collections 18
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAtomicNet ABC Proxy Service ABC Accounts API
OPEN COLLECTIONAtomicNet ABC Proxy Service ABC Memorials API
OPEN COLLECTIONAtomicNet ABC Proxy Service ABC Signing API
OPEN COLLECTIONAtomicNet ABC Proxy Service ABC Testnet API
OPEN COLLECTIONPolysign Asset API
OPEN COLLECTIONPolysign Authentication API
OPEN COLLECTIONAtomicNet API Server beneficiary authorization API
OPEN COLLECTIONPolysign book transfer API
OPEN COLLECTIONAtomicNet API Server book transfer confirmation API
OPEN COLLECTIONAtomicNet API Server escrow authorization API
OPEN COLLECTIONAtomicNet API Server Investor API
OPEN COLLECTIONPolysign Order API
OPEN COLLECTIONAtomicNet API Server Partner API
OPEN COLLECTIONAtomicNet API Server Settlement API
OPEN COLLECTIONAtomicNet API Server settlement confirmation API
OPEN COLLECTIONPolysign System API
OPEN COLLECTIONAtomicNet API Server Utility API
OPEN COLLECTIONScroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
polysign-mcp.yml
MCP SERVERSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for PolySign — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/polysign · machine-readable index on apis.io
This is an independent, third-party profile of PolySign, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.