Evervault API

Name: Evervault API
Brand: Evervault API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecuritySecrets Managementbasic43 EndpointsREST

For Agents

Encrypt and decrypt data, proxy outbound traffic through Evervault Relays, tokenize cards, run Functions, and manage webhooks via the full Evervault platform.

Install Jentic One Beta

Connect the Evervault API to your agent

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

Step 1: 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

Step 2: 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 API.

Encrypt and decrypt arbitrary payloads via POST /encrypt and POST /decrypt

Inspect a ciphertext to confirm it is Evervault-encrypted via POST /inspect

Proxy outbound HTTPS calls through Evervault Relays so PII is auto-tokenized in transit

GET STARTED

Start building with Evervault API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Evervault API for, with concrete tasks.

★ Outbound Relay for PII Tokenization

Companies that send sensitive data to many third-party APIs (CRMs, analytics, ML providers) route those requests through an Evervault Relay. The Relay receives plaintext, tokenizes or encrypts on the way out, and ensures partners only ever see safe representations. Setup is one Relay configuration plus optional custom domain mapping, dramatically reducing PII surface area without code changes per vendor.

POST /relays to create a Relay that tokenizes outbound calls to api.partner.com, then POST /relays/{relay_id}/custom-domains to map a branded subdomain

Encrypted Card Vault and Network Tokens

Merchants and platforms can store payment cards encrypted in Evervault and mint network tokens to authorise transactions without holding raw PANs themselves. The 43-endpoint surface includes operations for encryption, network tokenization, and Function-based card operations, supporting PCI scope reduction without rebuilding a card vault.

POST /encrypt with a card number, store the ciphertext in your DB, then later run an Evervault Function to mint a network token from the encrypted PAN

Webhooks-Driven Encrypted Workflows

Background jobs that depend on encrypted compute completing (Function runs, key rotations, Relay events) listen via Evervault webhooks. Agents register a webhook endpoint, then react to events by calling further Evervault operations or downstream services without polling.

Register a webhook URL on Evervault, then on receipt of a function-run.completed event call your downstream risk-scoring service with the run output

AI Agent Encryption Pipeline via Jentic

An AI assistant in a regulated workflow wraps every captured PII field with Evervault encryption before it lands in a database. Jentic exposes Evervault's full surface as MCP tools, so the agent searches by intent, picks the right operation, and runs it without ever seeing the raw API spec.

Use Jentic search 'encrypt cardholder data with Evervault' to find POST /encrypt, load schema, and execute on every card field captured in conversation

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/encrypt

Encrypt a payload

POST

/decrypt

Decrypt a payload

POST

/inspect

Inspect ciphertext metadata

POST

/functions/{function_name}/runs

Invoke a named Function

POST

/client-side-tokens

Mint a client-side decryption token

POST

/relays

Create a Relay

GET

/relays/{id}

Retrieve a Relay configuration

POST

/relays/{relay_id}/custom-domains

Attach a custom domain to a Relay

POST

/encrypt

Encrypt a payload

POST

/decrypt

Decrypt a payload

POST

/inspect

Inspect ciphertext metadata

POST

/functions/{function_name}/runs

Invoke a named Function

POST

/client-side-tokens

Mint a client-side decryption token

POST

Why Jentic?

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

Credential isolation

Evervault uses HTTP Basic with an app ID and API key; both are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped execution rights and never see the raw secrets, eliminating the risk of leaking credentials through prompts or logs.

Intent-based discovery

Agents search by intent (e.g. 'create an evervault relay' or 'encrypt cardholder data') and Jentic returns the matching Evervault operation with its full input schema, so the agent never has to browse vendor docs.

Time to first call

Direct Evervault integration: 2-4 days to set up Basic auth, Relays, and Function invocations cleanly. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using Evervault API through Jentic.

Why is there no official OpenAPI spec for Evervault API?

Evervault does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Evervault 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 API use?

The full Evervault API uses HTTP Basic auth with the app ID as username and an API key as password against api.evervault.com. Through Jentic, both credentials sit in the MAXsystem vault and are injected at call time.

Can I tokenize cards without taking on PCI scope using the Evervault API?

Yes. POST /encrypt accepts the raw PAN and returns ciphertext, while a Function or Relay can mint a network token from that ciphertext, so plaintext PANs never sit in your stack. Combine with /relays to keep outbound payment partner traffic in-scope only at Evervault's edge.

What are the rate limits for the Evervault API?

The OpenAPI spec does not declare specific limits; Evervault applies plan-based throttling. Inspect 429 responses and Retry-After headers and confirm your plan's ceiling with Evervault support before high-volume runs.

How do I create a Relay through Jentic?

Run pip install jentic, then await client.search('create an evervault relay'), client.load, client.execute. Jentic returns POST /relays with the Relay configuration schema (target URL, encryption rules) wired in for the agent to fill.

Can I confirm a value is Evervault-encrypted before calling /decrypt?

Yes. POST /inspect returns metadata about the ciphertext (whether it is Evervault-encrypted, the data role, and the encryption version) without revealing plaintext, so an agent can avoid wasted decrypt calls on malformed inputs.

Evervault API

Connect the Evervault API to your agent

Capabilities

Start building with Evervault API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs