How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Agentcard Identity verification API

Verify a connected user's identity: upload their ID, submit any extra fields we ask for, then show a short face scan.

Agentcard Identity verification API is one of 5 APIs that Agentcard publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Identity Verification. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.agentcard.sh.

5 operations 5 paths 2 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.agentcard.sh
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Agentcard Identity verification API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (platformToken). By default, every request must be authenticated.

  • platformToken — A platform access token. Get one on the Create an access token endpoint by exchanging your clientid + clientsecret, then send it as Authorization: Bearer . Tok…

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 1 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Identity verification 5

Verify a connected user's identity: upload their ID, submit any extra fields we ask for, then show a short face scan.

POST
/api/v2/kyc/documents/front
Upload the front of the ID
kycUploadFront body → 200400401404409422502
POST
/api/v2/kyc/documents/back
Upload the back of the ID
kycUploadBack body → 200400401404409422502
POST
/api/v2/kyc/information
Submit information
kycSubmitInformation body → 200400401404409502
GET
/api/v2/kyc
Get verification status
kycGetStatus 1 param → 200400401404409
POST
/api/v2/kyc/simulate
Simulate an outcome (test mode)
kycSimulate body → 200400401403404409502

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are KycState (6 properties), Error (1 property). Each schema is shown below with its type and property counts.

Error
object
Every v2 error uses the same envelope.
1 property
KycState
object
The single status contract every KYC response carries.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

agentcard-identity-verification-api-openapi.yml Raw ↑

Other APIs Agentcard publishes across the network.

Agentcard Authentication API
Agentcard Connect API
Agentcard Wallet funding API
Agentcard Withdrawals API
Where this information came from

This is an independent, third-party profile of Agentcard Identity verification API, 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.