canonical: https://jentic.com/apis/verifyd.online/verifyd-online

# Verifyd Online Verifyd API

API for identity verification and validation services. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a verification, list verifications. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Create a verification
- List verifications
- Get verification
- Query and filter Verifyd API records by parameters
- Monitor Verifyd API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Verifyd API to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including create a verification, list verifications, get verification.

Example prompt: Call POST /verifications to create a verification

### Automated Verifications Management

Automate verifications operations by combining multiple Verifyd API endpoints. Agents can list verifications and then get verification in a single workflow.

Example prompt: Call GET /verifications to list verifications, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Verifyd API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create a verification', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/verifications` | Create a verification |
| GET | `/verifications` | List verifications |
| GET | `/verifications/{id}` | Get verification |

## Key resources

- **Verifications** — Operations for verifications

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/verifyd.online/verifyd-online/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Verifyd API by hand means passing its key in the Authorization header against api.verifyd.online and coding each verification create and lookup call yourself. Through Jentic you install once, import the Verifyd API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Verifyd puts the verification id in the URL path (`/verifications/{id}`), so a rule can pin your agent to one verification. You choose the operations it may call, so it can create and read verifications only if you include those and nothing else.
- **Credential handling:** Your Verifyd API 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 'create a verification' or 'get a verification by id', and Jentic returns the matching Verifyd operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Verifyd API use?

The Verifyd API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a verification with the Verifyd API?

Yes. Use the POST /verifications endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Verifyd API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a verification through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a verification'. Jentic returns the matching Verifyd API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Verifyd API have?

The Verifyd API exposes 3 endpoints covering verifications operations.

### Can I limit what my agent is allowed to do with the Verifyd API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Verifyd operations your agent may call. You can grant only the operations you want, such as creating a verification with POST /verifications, listing verifications, or reading one with GET `/verifications/{id}`, and withhold the rest. Since the verification id sits in the URL path, you can also pin the agent to a single verification and control the API key it uses at execution time.