Temp Mail API
65
AI ReadinessAI-Aware (B)65/100
Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey8 EndpointsREST
For Agents
Programmatically domains list, get emails. Covers 8 operations with apiKey authentication.
Use for: I need to domains list, I want to emails, Search for one message, Find all source message
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Temporary disposable email API. Generate temporary email addresses using available domain names, receive emails, and manage messages. Messages are automatically deleted within 1-2 hours. Provided by Privatix Ltd via temp-mail.org. The API exposes 8 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Temp Mail API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Temp Mail 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.
1
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%2Ftemp-mail.org%2Ftemp-mail" | sh2
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%2Ftemp-mail.org%2Ftemp-mail" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Temp Mail API.
Domains list
Get emails
Source message
Delete message
Monitor Temp Mail API operational status and events
Use Cases
Patterns agents use Temp Mail API for, with concrete tasks.
★ Communications Operations
Use the Temp Mail API to perform communications operations programmatically. The API provides 8 endpoints covering core functionality including domains list, get emails, get one message.
Call GET /request/domains/ to domains list
Automated Domains Management
Automate domains operations by combining multiple Temp Mail API endpoints. Agents can get emails and then get one message in a single workflow.
Call GET /request/mail/id/{md5}/ to get emails, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Temp Mail 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.
Search Jentic for 'domains list', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
8 endpoints — temporary disposable email api.
METHOD
PATH
DESCRIPTION
GET
/request/domains/
Domains list
GET
/request/mail/id/{md5}/
Get emails
GET
/request/one_mail/id/{mail_id}/
Get one message
GET
/request/source/id/{mail_id}/
Source message
GET
/request/delete/id/{mail_id}/
Delete message
GET
/request/attachments/id/{mail_id}/
Get message attachments (legacy)
GET
/request/atchmnts/id/{mail_id}/
Get message attachments
GET
/request/one_attachment/id/{mail_id}/{atId}/
Get one attachment
GET
/request/domains/
Domains list
GET
/request/mail/id/{md5}/
Get emails
GET
/request/one_mail/id/{mail_id}/
Get one message
GET
/request/source/id/{mail_id}/
Source message
GET
/request/delete/id/{mail_id}/
Delete message
GET
/request/attachments/id/{mail_id}/
Get message attachments (legacy)
GET
/request/atchmnts/id/{mail_id}/
Get message attachments
GET
/request/one_attachment/id/{mail_id}/{atId}/
Get one attachment
Jentic AI Readiness Score
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.
T
Temp Mail API
- AI-Aware (B)65/100
73
Foundational Compliance63
Developer Experience & Jentic Compatibility55
AI-Readiness & Agent Experience94
Agent Usability50
Security69
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
91%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
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.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
4%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
47%
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.
55
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
69%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
69
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
69%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Temp Mail API by hand means provisioning its RapidAPI key, attaching that header to every call against the RapidAPI host, and building the mailbox polling and retry handling yourself. Through Jentic you install once, import the Temp Mail API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The Temp Mail API puts the mailbox id in the URL path (/request/one_mail/id/{mail_id}/), so a rule can pin your agent to one mailbox: it can read that mailbox's messages and attachments and nothing else. You choose the operations it may call, so destructive ones like deleting a message are not included unless you add them.
Credential isolation
Your Temp Mail 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.
Intent-based discovery
Agents search Jentic by intent such as 'list available domains' or 'read a temporary inbox', and Jentic returns the matching Temp Mail API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Temp Mail API through Jentic.
What authentication does the Temp Mail API use?
The Temp Mail API uses an API key passed in the `x-rapidapi-key` 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 domains list with the Temp Mail API?
Yes. Use the GET /request/domains/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Temp Mail 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 domains list through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'domains list'. Jentic returns the matching Temp Mail API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Temp Mail API have?
The Temp Mail API exposes 8 endpoints covering domains, messages, attachments operations.
Can I limit what my agent is allowed to do with the Temp Mail API?
Yes. Because you run Jentic One yourself, your own rules decide which Temp Mail API operations and credentials the agent may use. Since the mailbox id sits in the URL path, such as GET /request/one_mail/id/{mail_id}/, you can pin the agent to one mailbox so it only reads that inbox's messages and attachments and nothing else. You also choose the exact operations it may call, so a destructive one like GET /request/delete/id/{mail_id}/ stays out of reach unless you explicitly grant it.
GET STARTED