Envelope So Envelope API
55
AI ReadinessFoundational (C)55/100
Official vendor OpenAPI document · agent-readyProductivityCalendar SchedulingapiKey10 EndpointsREST
For Agents
Manage event guests and check-ins: list, create, update, and remove guests, register a guest, check guests in or out, and look up events over an x-api-key keyed API.
Use for: List all guests for an event, Create a new guest record, Check in a guest at the door, Register a guest for an event
Not supported: Does not sell tickets, process payments, or send invitations. Use for event guest and check-in management only.
The Envelope API manages events and their guests programmatically. An agent lists, creates, retrieves, updates, and removes guests, registers a guest, and checks a guest in or reverses a check-in at the door. It also lists events and retrieves an event by ID, so an assistant can run the guest side of an event from a single API keyed by an x-api-key header.
Install Jentic One Beta
Connect the Envelope API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Envelope 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%2Fenvelope.so%2Fenvelope" | 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%2Fenvelope.so%2Fenvelope" | 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 Envelope API.
List, create, and update guests for an event
Check a guest in and reverse a check-in at the door
Register a guest through the registration operation
Retrieve a single guest by ID
List events and retrieve an event by ID
Use Cases
Patterns agents use Envelope API for, with concrete tasks.
★ Agent-managed guest check-in
At the door, an agent looks up a guest by ID and checks them in, or reverses a check-in if someone was marked in error. The check-in and lookup operations are discovered through Jentic by intent, so a kiosk or assistant can process arrivals without wiring the API by hand.
Look up a guest by ID, check them in, and confirm the check-in state updated
Guest list building
Build and maintain an event's guest list by creating guests, updating their details, and registering new arrivals. An agent can add guests from an external source and keep each record current ahead of the event.
Create a new guest, update a field on an existing guest, and register a walk-in guest
Event lookup
Retrieve the events available in the account by listing them and fetching a single event by ID. An agent uses the event lookup to pick the right event before reading or updating its guests.
List the events in the account and retrieve one event's details by its ID
Key Endpoints
10 endpoints — the envelope api manages events and their guests programmatically.
METHOD
PATH
DESCRIPTION
GET
/v1/guests
List all guests
POST
/v1/guests
Create a new guest
GET
/v1/guests/{_id}
Get a guest by ID
PATCH
/v1/guests/{_id}
Update a guest
POST
/v1/guests/{_id}/check-in
Check in a guest
POST
/v1/guests/register
Register a guest
GET
/v1/events
List all events
GET
/v1/events/{_id}
Get an event by ID
GET
/v1/guests
List all guests
POST
/v1/guests
Create a new guest
GET
/v1/guests/{_id}
Get a guest by ID
PATCH
/v1/guests/{_id}
Update a guest
POST
/v1/guests/{_id}/check-in
Check in a guest
POST
/v1/guests/register
Register a guest
GET
/v1/events
List all events
GET
/v1/events/{_id}
Get an event by ID
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.
E
Envelope API
- Foundational (C)55/100
100
Foundational Compliance66
Developer Experience & Jentic Compatibility30
AI-Readiness & Agent Experience94
Agent Usability50
Security80
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
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.
66
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
14%
Example Density
How richly the API is illustrated with examples.
100%
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.
30
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
58%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
62%
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).
80
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
80%
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 Envelope API by hand means sending your key in the x-api-key header, targeting the envelope.so/api host, and sequencing guest, check-in, and event calls yourself. Through Jentic you install once, import the Envelope API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Envelope puts the guest id in the URL path (/v1/guests/{_id}), so a rule can pin your agent to one guest and the operations you pick. You choose the operations it may call, so destructive ones like deleting a guest are not included unless you add them.
Credential isolation
Your Envelope 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 'check in a guest' or 'list event guests', and Jentic returns the matching Envelope 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 Envelope API through Jentic.
What authentication does the Envelope API use?
The Envelope API authenticates with an API key sent in the x-api-key header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I check guests in with the Envelope API?
Yes. The check-in operation marks a guest as checked in, and a companion operation reverses a check-in, so an agent can process arrivals and correct mistakes at the door for a guest looked up by ID.
What are the rate limits for the Envelope API?
The OpenAPI spec does not state request rate limits. Check the Envelope documentation at https://docs.envelope.so for current limits and any per-key quotas.
Is there an Envelope MCP server?
You don't need an MCP server to give your agent the Envelope API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the guest, check-in, and event operations it needs.
Can I limit what my agent is allowed to do with the Envelope API?
Yes. Because Envelope carries the guest id in the URL path, you can pin a rule to one guest and allow only the check-in and read operations, so a door assistant can check guests in but cannot delete guest records. Destructive operations stay off unless you add them, and every call the agent makes is logged.
How do I check in a guest through Jentic?
Search Jentic for 'check in a guest', and it returns the Envelope check-in operation with its input schema; your agent supplies the guest ID and calls it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED