Evervault Encryption API

Name: Evervault Encryption API API
Brand: Evervault Encryption API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecuritySecrets ManagementapiKey4 EndpointsREST

For Agents

Encrypt and decrypt sensitive data, run encrypted serverless Functions, and mint client tokens through Evervault's encryption-as-a-service.

Connect the Evervault Encryption API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Evervault Encryption 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Evervault Encryption API API.

Encrypt arbitrary JSON payloads server-side via POST /encrypt before storing them

Decrypt previously encrypted Evervault payloads with POST /decrypt for downstream processing

Invoke an Evervault Function by name to run encrypted compute via /functions/{functionName}/runs

Mint a short-lived client token via POST /client-tokens so browsers can decrypt selected fields

GET STARTED

Start building with Evervault Encryption API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Evervault Encryption API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Evervault Encryption API, keeping it validated and agent-ready. Evervault provides encryption-as-a-service for sensitive data such as PII, payment details, and health records. The four-endpoint surface lets agents encrypt and decrypt payloads server-side, run Evervault Functions for serverless encrypted compute, and mint client-tokens for safe client-side decryption. Together the endpoints let an application keep plaintext out of databases without rebuilding key management in-house.

Use Cases

Patterns agents use Evervault Encryption API API for, with concrete tasks.

★ PII Tokenization at the Edge

Applications that collect SSNs, dates of birth, or government IDs must keep plaintext out of their primary database and logs. Evervault's /encrypt endpoint accepts JSON containing sensitive fields and returns an opaque ciphertext that is safe to store. The /decrypt endpoint reverses the process inside trusted code paths, leaving the plaintext exposed for the shortest possible window.

POST /encrypt with the JSON payload {"ssn":"123-45-6789"} and store the returned ciphertext in the customers table

Encrypted Serverless Compute

Some workloads need to operate on sensitive data without the host service ever seeing the plaintext (e.g. computing risk scores from raw card data). Evervault Functions let an agent invoke a named function with an encrypted payload via /functions/{functionName}/runs and receive the result, with decryption happening only inside the Function's secure runtime.

POST /functions/risk-score/runs with an encrypted card payload and read the returned risk score without ever decrypting the card client-side

Client-Side Selective Decryption

Customer-facing dashboards sometimes need to reveal a single field — say, the last four digits of a stored card — without proxying every page render through the backend. Minting a short-lived client-token via POST /client-tokens authorizes the browser to decrypt only the named ciphertext for a few minutes, then expires automatically.

POST /client-tokens scoped to a specific encrypted card record and pass the token to the browser to decrypt only the last four digits

Agent-Driven Data Protection via Jentic

An AI assistant in a fintech app needs to handle sensitive customer data without the LLM context ever holding plaintext. Jentic exposes Evervault's /encrypt operation as an MCP tool so the agent can wrap any sensitive value before it touches downstream systems, and decrypt only inside controlled paths.

Use Jentic search 'encrypt sensitive data with Evervault' to find POST /encrypt, load schema, and execute on every PII field captured during a chat

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for evervault encryption api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/encrypt

Encrypt a JSON payload

POST

/decrypt

Decrypt a previously encrypted payload

POST

/functions/{functionName}/runs

Invoke a named Evervault Function

POST

/client-tokens

Mint a client-side decryption token

POST

/encrypt

Encrypt a JSON payload

POST

/decrypt

Decrypt a previously encrypted payload

POST

/functions/{functionName}/runs

Invoke a named Evervault Function

POST

/client-tokens

Mint a client-side decryption token

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Evervault apiKey is stored encrypted in the Jentic MAXsystem vault. Agents receive scoped execution rights and never see the raw key, so plaintext credentials never enter the LLM context window.

Intent-based discovery

Agents search by intent (e.g. 'encrypt sensitive data with Evervault') and Jentic returns POST /encrypt with its full input schema, removing the need to browse vendor docs.

Time to first call

Direct Evervault integration: 1-2 days to wire encryption, decryption, and Function invocation safely. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Evervault API

Wider 43-endpoint Evervault surface adding relays, payment cards, and webhooks.

Use this when you need relay proxying, card tokenization, or webhook configuration alongside encryption.

Complementary

Stripe API

Stripe handles the full payments lifecycle while Evervault encrypts the surrounding PII.

Pair with Stripe when card data is processed by Stripe but additional customer PII (SSNs, IDs) needs encryption-at-rest.

Alternative

Cloudflare API

Cloudflare offers WAF and SSL controls but not field-level encryption-as-a-service.

Choose Cloudflare for transport-level protection; choose Evervault when individual fields need to be unreadable inside your own infrastructure.

FAQs

Specific to using Evervault Encryption API API through Jentic.

Why is there no official OpenAPI spec for Evervault Encryption API?

Evervault does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Evervault Encryption API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Evervault Encryption API use?

The API uses an apiKey credential carried over HTTP headers. Through Jentic, the key sits in the MAXsystem vault and is injected at call time so it never enters the agent's context window.

Can I encrypt a credit card number with the Evervault Encryption API?

Yes. POST /encrypt with the card number inside a JSON payload and Evervault returns an opaque ciphertext that is safe to store. Decrypt later with POST /decrypt or compute on it inside an Evervault Function without exposing plaintext to your stack.

What are the rate limits for the Evervault Encryption API?

The OpenAPI spec does not declare quantitative rate limits; Evervault applies plan-based throttling. Watch 429 responses and confirm your account ceiling with Evervault support before high-throughput workloads.

How do I encrypt a payload through Jentic?

Run pip install jentic, then await client.search('encrypt sensitive data with Evervault'), client.load, client.execute. Jentic returns POST /encrypt with its JSON payload schema so the agent can pass the field directly.

How are Evervault Functions different from /encrypt and /decrypt?

Functions run named serverless code at /functions/{functionName}/runs that operates on encrypted inputs and returns derived outputs without the host ever seeing plaintext. /encrypt and /decrypt only transform values, while Functions perform compute on top of them.