Evervault APIs for AI Agents
SecuritySecrets ManagementJentic-Generated SpecsBasic authAPI keyAgent Ready
Evervault API Catalog
2 APIs across 1 product group.
Security2
Evervault APIEncrypt and decrypt data, proxy outbound traffic through Evervault Relays, tokenize cards, run Functions, and manage webhooks via the full Evervault platform.~43 endpointsEvervault Encryption APIEncrypt and decrypt sensitive data, run encrypted serverless Functions, and mint client tokens through Evervault's encryption-as-a-service.~4 endpoints
Which Evervault API should I use?
| I want to... | Use | Why |
|---|---|---|
| Core encrypt, decrypt, Functions, and client tokens only | Evervault Encryption API | The four-endpoint surface covers the encryption primitives without the wider platform operations. |
| Relays, card tokenization, inspect, webhooks, and custom domains | Evervault API | The 43-endpoint surface adds outbound proxying, network tokens, and event configuration on top of encrypt and decrypt. |
Install Jentic One Beta
Connect the Evervault APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Evervault APIs, 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%2Fevervault.com" | 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%2Fevervault.com" | 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.
Once connected, ask your agent something like: “protect sensitive data with Evervault encryption and Relays”.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Evervault by hand means handling its auth against api.evervault.com and coding the encrypt, decrypt, Function-run, and Relay calls across two surfaces yourself. With Jentic One installed, your agent finds and adds either Evervault API from the Jentic directory, stores the credentials once, and calls it.
Permission scoping
Evervault takes data in the request body and resource ids such as the relay id in the URL path, so your own rules in Jentic One can pin the agent to specific operations. Decrypt or Relay creation are not available to the agent unless you add them to the allowed set.
Credential isolation
Your Evervault credentials are stored encrypted by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context window.
FAQs
Specific to using Evervault APIs through Jentic.
What is the difference between the two Evervault APIs?
The encryption surface is a slim four-endpoint API covering encrypt, decrypt, Functions, and client tokens. The full Evervault API is a 43-endpoint surface that adds Relays, card and network tokenization, ciphertext inspection, webhooks, and custom domains. Choose the slim surface for core encryption primitives and the full one when you need proxying or platform operations.
Does one Evervault account work across both APIs?
Yes. Both APIs call api.evervault.com and use your Evervault app credentials, so a single account covers both. The encryption surface is presented with an apiKey header while the full platform uses HTTP Basic auth with the app ID as username and the API key as password.
Why does Jentic publish these specs?
Evervault does not publish an official OpenAPI specification. Jentic generates and maintains both specs so agents and developers can call Evervault through structured tooling. They are validated against the live API and kept up to date.
How do the APIs keep plaintext out of my stack?
Encrypt returns opaque ciphertext that is safe to store, Functions compute over encrypted inputs without the host seeing plaintext, and Relays tokenize or encrypt data on the way to partners. Decryption happens only inside trusted code paths or briefly in the browser via short-lived client tokens.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
