canonical: https://jentic.com/apis/c-me.com/c-me # C-Me API 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. ## For AI agents Start a KYC verification for a user and poll the verification result by ID through the C-Me identity verification API. ## Scope Does not handle authentication sessions, password resets, or fraud transaction monitoring - use for one-shot identity verification and KYC checks only. ## Capabilities - 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 - Drop a KYC step into an onboarding agent flow with two HTTP operations ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | Method | Path | Description | | --- | --- | --- | | POST | /verifications | Start a new identity verification | | GET | /verifications/{id} | Get the status and result of a verification | ## Key resources - **verifications** — Create a new identity verification session and retrieve its status by ID. ## Why Jentic - **Setup:** Wiring the C-Me API by hand means placing your key in the Authorization header on every request and polling the verification result by id after you submit a check. Through Jentic you install once, import C-Me from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** C-Me puts the verification id in the URL path (/verifications/{id}), so a rule can pin your agent to reading a specific verification result. You choose the operations it may call, so submitting a new verification on /verifications is not included unless you add it. - **Credential handling:** 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. - **Discovery method:** 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. ## Related APIs - **Caller API** — Caller API enriches phone numbers with carrier and identity data, useful alongside C-Me document verification for layered identity checks. - **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. - **Calm API** — Both expose narrow API key authenticated services, but Calm delivers wellness content rather than identity verification. ## FAQ ### 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.