Install Jentic One Beta

Connect the EmailVerify to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EmailVerify, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaypi.dev%2Fpaypi" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaypi.dev%2Fpaypi" | 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 EmailVerify API.

Send one-time verification codes to any email address with managed delivery

Validate submitted codes against issued OTPs with expiry enforcement

Offload email delivery infrastructure to a managed service

Track verification code lifecycle from issuance through validation or expiry

Integrate email-based two-factor authentication into signup or login flows

GET STARTED

Start building with EmailVerify API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use EmailVerify API for, with concrete tasks.

★ User Registration Email Verification

Verify new user email addresses during account registration by sending a one-time code and validating it when the user submits. EmailVerify handles the email delivery and code management, so developers do not need to configure SMTP servers or implement code expiry logic. The API confirms verification in a single response.

Send a verification code to user@example.com via POST /sendCode and then validate the submitted code using POST /checkCode

Two-Factor Authentication via Email

Add email-based second factor to login flows by issuing a one-time code when a user attempts to sign in. The code is sent to their registered email and must be submitted back for validation before the session is granted. EmailVerify manages delivery and expiry automatically.

Issue an OTP to the user's registered email via POST /sendCode and validate their response with POST /checkCode before granting session access

AI Agent Email Verification Orchestration

AI agents use EmailVerify through Jentic to verify email addresses as part of automated onboarding or identity confirmation workflows. Jentic handles credential management and operation discovery so agents can trigger email verification without configuring email infrastructure.

Search Jentic for 'send email verification code', load the sendCode operation schema, and execute to send an OTP to a target email address

Key Endpoints

2 endpoints — emailverify by paypi is an otp email verification service that sends one-time codes to email addresses and validates them.

METHOD

PATH

DESCRIPTION

POST

/sendCode

Send a verification code to an email address

POST

/checkCode

Validate a submitted verification code

POST

/sendCode

Send a verification code to an email address

POST

/checkCode

Validate a submitted verification code

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring EmailVerify by hand means learning its bearer token auth and coding the two-step send-then-check flow against its OTP endpoints yourself. Through Jentic you install once, import EmailVerify from the API Directory, store the token once, and your agent calls it.

Permission scoping

EmailVerify takes the email and code in the request body rather than the URL path, so limit the agent to the operations it needs, such as sending a code or checking a code. You choose which of those two operations it may call, and it can call nothing else.

Credential isolation

Your EmailVerify bearer token 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 an email address with a one-time code' or 'check a submitted OTP', and Jentic returns the matching EmailVerify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using EmailVerify API through Jentic.

What authentication does the EmailVerify API use?

EmailVerify uses Bearer token authentication. Include your API token in the Authorization header as 'Bearer {token}' with each request to POST /sendCode and POST /checkCode. Through Jentic, tokens are stored encrypted in your Jentic One instance and agents receive scoped access without handling raw credentials.

Can I use EmailVerify for two-factor authentication?

Yes. Call POST /sendCode with the user's email address to issue a one-time code, then validate the code they submit via POST /checkCode. The API handles code generation, email delivery, and expiry enforcement, making it suitable for 2FA login flows.

What are the rate limits for the EmailVerify API?

The EmailVerify specification does not document explicit rate limits. The service is designed for transactional verification flows (one code per user action) rather than bulk email sending. Contact PayPI for volume-specific limits.

How do I verify an email address through Jentic?

Use Jentic to search for the operation 'send email verification code', load the schema for POST /sendCode, and execute with the target email address. Then search for 'check email verification code', load POST /checkCode, and submit the code the user provides. Jentic handles authentication for both calls.

Does EmailVerify handle the email delivery infrastructure?

Yes. EmailVerify sends the verification emails directly - you do not need to configure SMTP servers, email templates, or delivery tracking. The API manages the full lifecycle from code generation through email delivery and validation.

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

Yes. Because you run Jentic One yourself, your own rules decide which EmailVerify operations and credentials the agent may use. EmailVerify exposes just two operations, sending a code via POST /sendCode and validating one via POST /checkCode, and you choose which of those the agent is permitted to call. Since the email address and code travel in the request body rather than the URL path, the agent can only reach the operations you have allowed and nothing else.

Paypi EmailVerify

AI ReadinessNon-Ready (F)34/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationbearer2 EndpointsREST

For Agents

Send OTP verification codes to email addresses and validate them for user authentication flows without managing email infrastructure.

Use for: I need to verify a user's email address with a one-time code, Send an OTP verification code to an email address, Check whether a submitted verification code is valid, I want to add email verification to my signup flow

Not supported: Does not handle SMS verification, push notifications, or email delivery beyond OTP codes - use for email-based one-time code verification only.

EmailVerify by PayPI is an OTP email verification service that sends one-time codes to email addresses and validates them. The API handles email delivery infrastructure and code lifecycle management, providing a simple 2-endpoint interface for sending verification codes and checking their validity. It eliminates the need for developers to set up email systems or track verification states.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: FSignals: 4

Example Density

How richly the API is illustrated with examples.

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

23%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

33%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the EmailVerify to your agent

Capabilities

Start building with EmailVerify API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Paypi EmailVerify

Jentic AI Readiness Score

EmailVerify

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness