C-Me API

Name: C-Me API API
Brand: C-Me API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity VerificationapiKey2 EndpointsREST

For Agents

Start a KYC verification for a user and poll the verification result by ID through the C-Me identity verification API.

Quickstart

Get started with C-Me API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"verify a user identity"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with C-Me API API.

Initiate an identity verification session by posting personal details to /verifications

Retrieve the status and outcome of a verification using its verification ID

Track verification lifecycle from submission to final pass or fail decision

Authenticate every request using a per-account API key in the Authorization header

GET STARTED

Start building with C-Me API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for C-Me API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for C-Me API, keeping it validated and agent-ready. C-Me is an identity verification and KYC service that runs document and biometric checks on end users. The API is intentionally narrow with two operations — POST /verifications to start a verification session for a person and GET /verifications/{id} to poll its status and retrieve the result. Authentication is an API key passed in the Authorization header, making it straightforward to drop into onboarding or risk-review agents that need a yes/no identity decision.

Use Cases

Patterns agents use C-Me API API for, with concrete tasks.

★ User Onboarding KYC Step

Trigger an identity verification at signup by posting the new user's details to /verifications, then poll /verifications/{id} until the status moves out of pending. The response indicates whether the user is cleared to access the product, blocked, or needs manual review. Suitable for fintech, marketplace, and regulated SaaS onboarding flows.

POST a verification to /verifications with the user's name and document fields, then poll GET /verifications/{id} every 5 seconds until status is no longer pending.

Risk Review Re-Verification

When an account is flagged for unusual activity, re-run identity verification on the existing user by submitting a new POST /verifications request and storing the new verification ID against the user record. The historic record of GET /verifications/{id} responses gives compliance teams an audit trail of every check performed.

POST a new verification for the flagged user and link the returned verification ID to the risk case.

Verification Result Polling

Retrieve the final result of an asynchronous verification by calling GET /verifications/{id}. The agent should poll on a backoff and stop when status reaches a terminal value, then surface the decision and any failure reasons to the downstream workflow. This avoids blocking the original signup HTTP request on a long-running check.

Call GET /verifications/{id} with exponential backoff until the status field reaches a terminal value, then return the decision.

AI Agent KYC Integration via Jentic

Through Jentic, an AI agent searches for an intent like 'verify a user identity' and is returned the C-Me verifications operation along with its input schema. The agent calls the operation with the supplied fields, then loads the GET-by-ID schema to poll the result, all without ever holding the raw Authorization header value. Setup time is under an hour versus a few days of direct integration.

Use Jentic search for 'verify a user identity', execute the C-Me POST /verifications operation, then load the polling schema and execute it with the returned ID.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for c-me api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/verifications

Start a new identity verification

GET

/verifications/{id}

Get the status and result of a verification

POST

/verifications

Start a new identity verification

GET

/verifications/{id}

Get the status and result of a verification

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The C-Me Authorization header value is held encrypted in the Jentic vault. Agents reference the operation by name and Jentic injects the header at execution — the raw key never appears in agent prompts, logs, or model context.

Intent-based discovery

Agents search Jentic by intent (for example 'verify a user identity' or 'check a KYC result') and Jentic returns the matching C-Me operation with its input schema, so the agent can call the right endpoint without browsing C-Me documentation.

Time to first call

Direct C-Me integration: 1-3 days for auth wiring, polling logic, and webhook or status handling. Through Jentic: under 1 hour — search for the operation, load its schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Caller API

Caller API enriches phone numbers with carrier and identity data, useful alongside C-Me document verification for layered identity checks.

Use Caller API as a lightweight phone-based identity signal before triggering a full C-Me document and biometric check.

Complementary

Call Control API

Call Control supplies phone reputation data that can feed into a risk score before deciding whether to run a full C-Me KYC.

Run Call Control checks for low-cost pre-screening, then escalate to C-Me when the phone reputation signal is inconclusive.

Alternative

Calm API

Both expose narrow API key authenticated services, but Calm delivers wellness content rather than identity verification.

Not a real alternative for KYC — listed only for agents comparing third-party API key services with similar auth patterns.

FAQs

Specific to using C-Me API API through Jentic.

Why is there no official OpenAPI spec for C-Me API?

C-Me publishes documentation on Stoplight but does not host an OpenAPI specification on their own developer site. Jentic generates and maintains this spec so that AI agents and developers can call C-Me API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the C-Me API use?

The C-Me API uses an API key passed in the Authorization HTTP header. Through Jentic, the key is stored encrypted in the credential vault and injected at execution time, so the agent never holds the raw value.

Can I check the status of a verification with the C-Me API?

Yes. After creating a verification with POST /verifications, retrieve its status by calling GET /verifications/{id} with the returned verification ID. The agent should poll until the status reaches a terminal value rather than blocking on the initial POST.

What are the rate limits for the C-Me API?

Rate limits are not declared in the OpenAPI specification and are managed at the account level by C-Me. For high-volume onboarding flows, contact C-Me support for the limits applied to your API key before scheduling batch verifications.

How do I run a KYC check with the C-Me API through Jentic?

Install the SDK with pip install jentic, run a search for 'verify a user identity', load the schema for POST /verifications, and execute it with the user details. Then load and execute the GET /verifications/{id} schema to retrieve the decision.

Is the C-Me API free?

C-Me prices identity verification per check rather than offering a free tier. Pricing is not declared in the OpenAPI spec and depends on the verification types enabled on the account — contact C-Me for current per-check rates.