Polygon ID
Polygon ID (now operating as Privado ID) is a self-sovereign identity platform that enables issuers to create and manage decentralized identifiers (DIDs) and verifiable credentials (VCs) using zero-knowledge proof cryptography. Built on the iden3 protocol and the Polygon blockchain, it allows organizations to issue privacy-preserving credentials — such as KYC attestations, age proofs, and reputation signals — while giving users full control over their identity data. Verifiers can authenticate users and gate access using ZK queries without learning underlying personal information.
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 Polygon ID the way a machine reads it — 144 machine-readable artifacts across 2 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 — Polygon ID scores 38.1/100 (thin), with a separate agent-readiness read of 22/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Polygon ID'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/polygon-id/"
title="Polygon ID on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/polygon-id.svg"
alt="Polygon ID Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/polygon-id/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/polygon-id/"
title="Polygon ID on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/polygon-id/card.svg"
alt="Polygon ID 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 Polygon ID
Each block below is one kind of artifact we hold for Polygon ID. 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.
Polygon ID Verifier SDK
The Verifier SDK enables web2 and web3 applications to authenticate users based on verifiable credentials without accessing the underlying personal data. Verifiers compose ZK qu...
Polygon ID JavaScript SDK
The JS-SDK enables browser-based applications, extensions, and dApps to implement identity wallet functionality, create and manage DIDs, generate ZK proofs, and interact with th...
Polygon ID Wallet SDK (Flutter)
Flutter plugin for integrating Polygon ID wallet capabilities into mobile applications. Provides identity creation, credential storage, ZK proof generation, and protocol communi...
Polygon ID Agent API
Collection of endpoints related to Mobile
Polygon ID Auth API
The Auth API from Polygon ID — 3 operation(s) for auth.
Polygon ID Config API
The Config API from Polygon ID — 2 operation(s) for config.
Polygon ID Connection API
The Connection API from Polygon ID — 5 operation(s) for connection.
Polygon ID Credentials API
Collection of endpoints related to Credentials
Polygon ID Display Methods API
The Display Methods API from Polygon ID — 2 operation(s) for display methods.
Polygon ID Identity API
Collection of endpoints related to Identity
Polygon ID Internal API
Internal endpoints
Polygon ID Key Management API
Collection of endpoints related to Key Management
Polygon ID Links API
The Links API from Polygon ID — 4 operation(s) for links.
Polygon ID Payment API
The Payment API from Polygon ID — 6 operation(s) for payment.
Polygon ID Public API
Public endpoints for integrators
Polygon ID QR Store API
The QR Store API from Polygon ID — 1 operation(s) for qr store.
Polygon ID Schemas API
The Schemas API from Polygon ID — 2 operation(s) for schemas.
Scroll within the panel for all 17 ·
Open Collections 15
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 COLLECTIONPrivado ID - Issuer Agent API
OPEN COLLECTIONPrivado ID - Issuer Agent Auth API
OPEN COLLECTIONPrivado ID - Issuer Agent Config API
OPEN COLLECTIONPrivado ID - Issuer Agent Connection API
OPEN COLLECTIONPrivado ID - Issuer Agent Credentials API
OPEN COLLECTIONPrivado ID - Issuer Agent Display Methods API
OPEN COLLECTIONPrivado ID - Issuer Agent Identity API
OPEN COLLECTIONPrivado ID - Issuer Agent Internal API
OPEN COLLECTIONPrivado ID - Issuer Agent Key Management API
OPEN COLLECTIONPrivado ID - Issuer Agent Links API
OPEN COLLECTIONPrivado ID - Issuer Agent Payment API
OPEN COLLECTIONPrivado ID - Issuer Agent Public API
OPEN COLLECTIONPrivado ID - Issuer Agent QR Store API
OPEN COLLECTIONPrivado ID - Issuer Agent Schemas API
OPEN COLLECTIONScroll within the panel for all 15 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Polygon Id Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Polygon ID API Rules
SPECTRALJSON Schema 91
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AgentResponse
JSON SCHEMAAuthenticationConnection
JSON SCHEMAAuthenticationResponse
JSON SCHEMABasicMessage
JSON SCHEMAConnectionsPaginated
JSON SCHEMACreateAuthCredentialRequest
JSON SCHEMACreateConnectionRequest
JSON SCHEMACreateCredentialRequest
JSON SCHEMACreateCredentialResponse
JSON SCHEMACreateDisplayMethodRequest
JSON SCHEMACreateIdentityRequest
JSON SCHEMACreateIdentityResponse
JSON SCHEMACreateKeyRequest
JSON SCHEMACreateKeyResponse
JSON SCHEMACreateLinkRequest
JSON SCHEMACreatePaymentRequestResponse
JSON SCHEMACreatePaymentRequest
JSON SCHEMACredentialLinkQrCodeResponse
JSON SCHEMACredentialOfferResponse
JSON SCHEMACredentialSchema
JSON SCHEMACredentialSubject
JSON SCHEMACredential
JSON SCHEMACredentialsPaginated
JSON SCHEMADisplayMethodEntity
JSON SCHEMADisplayMethodPaginated
JSON SCHEMADisplayMethod
JSON SCHEMAEncryptedVC
JSON SCHEMAGenericErrorMessage
JSON SCHEMAGenericMessage
JSON SCHEMAGetAuthenticationConnectionResponse
JSON SCHEMAGetConnectionResponse
JSON SCHEMAGetConnectionsResponse
JSON SCHEMAGetIdentitiesResponse
JSON SCHEMAGetIdentityDetailsResponse
JSON SCHEMAGetPaymentRequestsResponse
JSON SCHEMAHealth
JSON SCHEMAIdentityState
JSON SCHEMAImportSchemaRequest
JSON SCHEMAIssuerDescription
JSON SCHEMAKey
JSON SCHEMAKeysPaginated
JSON SCHEMALinkSimple
JSON SCHEMALink
JSON SCHEMANetworkData
JSON SCHEMAOffer
JSON SCHEMAPaginatedMetadata
JSON SCHEMAPaymentOptionConfigItem
JSON SCHEMAPaymentOptionConfig
JSON SCHEMAPaymentOptionRequest
JSON SCHEMAPaymentOption
JSON SCHEMAPaymentOptionsPaginated
JSON SCHEMAPaymentOptions
JSON SCHEMAPaymentRequestInfo
JSON SCHEMAPaymentStatus
JSON SCHEMAPaymentVerifyRequest
JSON SCHEMAPaymentsConfiguration
JSON SCHEMAPublishIdentityStateResponse
JSON SCHEMARefreshService
JSON SCHEMARevocationStatusResponse
JSON SCHEMARevokeClaimResponse
JSON SCHEMASchema
JSON SCHEMAStateStatusResponse
JSON SCHEMAStateTransaction
JSON SCHEMAStateTransactionsPaginated
JSON SCHEMAStateTransactions
JSON SCHEMASupportedNetworks
JSON SCHEMATimeUTC
JSON SCHEMAUpdatePaymentOptionRequest
JSON SCHEMAUUIDResponse
JSON SCHEMAUUIDString
JSON SCHEMABody
JSON SCHEMACallbackResponse
JSON SCHEMAGenericErrorMessage
JSON SCHEMAHealth
JSON SCHEMAJWZMetadata
JSON SCHEMAJWZProofs
JSON SCHEMAQRCode
JSON SCHEMAQRStoreRequest
JSON SCHEMAQRStoreResponse
JSON SCHEMAQuery
JSON SCHEMAScopeParams
JSON SCHEMAScopeRequest
JSON SCHEMAScope
JSON SCHEMASignInRequest
JSON SCHEMASingInResponse
JSON SCHEMAStatusResponse
JSON SCHEMATransactionDataResponse
JSON SCHEMATransactionData
JSON SCHEMAUUID
JSON SCHEMAVerifiablePresentation
JSON SCHEMAVerifiablePresentations
JSON SCHEMAScroll within the panel for all 91 ·
Examples 13
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 13 ·
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Polygon ID — 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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/polygon-id · machine-readable index on apis.io
This is an independent, third-party profile of Polygon ID, 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.