C-Me API

Name: C-Me 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.

Install Jentic One Beta

Connect the C-Me API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the C-Me API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with C-Me 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

GET STARTED

Start building with C-Me API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use C-Me 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 Jentic?

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

Credential isolation

Your C-Me Authorization key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'verify a user identity' or 'check a KYC result', and Jentic returns the matching C-Me operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using C-Me 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the C-Me API?

Yes. Jentic One is self-hosted, so your own rules decide which C-Me operations and credentials your agent may use. Because C-Me puts the verification id in the URL path at GET /verifications/{id}, you can pin the agent to reading a specific verification result, and you choose the operations it may call, so submitting a new check via POST /verifications is excluded unless you add it. Your C-Me Authorization key is held by your own instance and injected only when an allowed call runs.