# set a secretvestauth agent curl https://as2.dotenvx.com/set -d '{"KEY":"value"}'# get all secretsvestauth agent curl "https://as2.dotenvx.com/get"# get single secretvestauth agent curl "https://as2.dotenvx.com/get?key=KEY"# get multiple secretsvestauth agent curl "https://as2.dotenvx.com/get?key=KEY,TWILIO"
`Docle` Check if email address is real
Check if an email address is real before you hit send. Verifies syntax, DNS, MX records, SMTP mailbox existence, and cross-references multiple providers. All in real time, no signup required.
…the agents sign HTTP requests with a drop-in curl wrapper.
> SIGNED - 200$ vestauth agent curl https://api.vestauth.com/whoami{"uid":"agent-4b94ccd425e939fac5016b6b",...}
learn more
vestauth agent curl autosigns curl requests – injecting valid signed headers according to the web-bot-auth draft. You can peek these with the built-in headers primitive.
Change HOSTNAME to its production url - e.g. vestauth.yoursite.com
Change DATABASE_URL to a managed postgres - e.g. postgresql://USER:PASS@aws-1-us-east-1.pooler.supabase.com:5432/postgres
production note
[!WARNING]
Production note: Configure a wildcard DNS record for *.${HOSTNAME}.
Example: if HOSTNAME=vestauth.yourapp.com, add *.vestauth.yourapp.com.
Required for .well-known discovery per the web-bot-auth spec.
Advanced
Become a vestauth power user.
CLI 📟
Advanced CLI commands.
`agent init`
Create agent.
$ vestauth agent init✔ agent created (.env/AGENT_UID=agent-609a4fd2ebf4e6347108c517)⮕ next run: [vestauth agent curl https://api.vestauth.com/whoami]
`agent init --hostname`
Use --hostname to override the agent API hostname (defaults to AGENT_HOSTNAME, then api.vestauth.com):
When no scheme is provided, https:// is assumed. For local non-TLS endpoints, pass http://... explicitly.
$ vestauth agent init --hostname https://vestauth.yoursite.com✔ agent created (.env/AGENT_UID=agent-609a4fd2ebf4e6347108c517)⮕ next run: [vestauth agent curl https://api.vestauth.com/whoami]
$ vestauth server db:dropDropped database 'vestauth_production'
`server start`
Start vestauth server.
$ vestauth server startvestauth server listening on http://localhost:3000
`server start --port`
Start vestauth server on specific port.
$ vestauth server start --port 4567vestauth server listening on http://localhost:4567
`server start --hostname`
Specify hostname for vestauth server (default: localhost:3000).
$ vestauth server start --hostname vestauth.yoursite.comvestauth server listening on https://vestauth.yoursite.com
`server start --database-url`
Specify database url for vestauth server (default: localhost/vestauth_production).
$ vestauth server start --database-url postgresql://USER:PASS@aws-1-us-east-1.pooler.supabase.com:5432/postgresvestauth server listening on http://localhost:3000
Vestauth gives agents a cryptographic identity and a simple way to authenticate HTTP requests. Most agent systems rely on API keys, bearer tokens, or username/passwords. These approaches are difficult to rotate, easy to leak, and hard to attribute to a specific agent. Vestauth replaces shared secrets with public/private key cryptography. Agents sign requests using a private key, and tools verify those requests using the agent's public key. All built on open internet standards. It's elegant and the future.
Defines headers and authentication architecture for autonomous agents
Vestauth follows these specifications to ensure interoperability between agents and tools while avoiding vendor lock-in. Vestauth focuses on developer ergonomics while staying compliant with these emerging standards.
Compare
Agent + Tool Matrix – Compare Vestauth vs existing auth.
Capability
Vestauth
API Keys
OAuth
Cookies
Agent: no browser required
✅
✅
⚠️ (depends on flow)
❌
Agent: easy to automate
✅
✅
⚠️
❌
Agent: no shared secret
✅
❌
⚠️ (bearer tokens)
❌
Agent: per‑request identity proof
✅
❌
⚠️ (token‑based)
❌
Agent: easy key/token rotation
Legend: ✅ strong fit, ⚠️ partial/conditional, ❌ poor fit
How It Works
An agent generates a public/private keypair.
The agent signs each HTTP request with its private key.
The tool verifies the signature using the agent’s public key.
Requests are attributable, auditable, and do not require shared secrets or browser sessions.
FAQ
What problem does Vestauth solve?
Vestauth gives agents a cryptographic identity and a simple way to authenticate HTTP requests.
Most agent systems rely on API keys, bearer tokens, or username/passwords. These approaches are difficult to rotate, easy to leak, and hard to attribute to a specific agent.
Vestauth replaces shared secrets with public/private key cryptography. Agents sign requests using a private key, and tools verify those requests using the agent's public key.
API keys are shared secrets. Anyone who obtains the key can impersonate the client, and keys are difficult to rotate safely.
Vestauth uses cryptographic signing instead of shared secrets. This allows tools to verify identity without storing or distributing sensitive credentials.
Where are agent keys stored?
Agent keys are generated locally and stored in the agent's environment configuration (.env).
AGENT_PRIVATE_JWK is used to sign requests and must never be shared.
AGENT_PUBLIC_JWK is safe to publish and is used by tools for verification.
Is Vestauth only for AI agents?
No.
Vestauth can authenticate any automated system including:
developer tools
CLIs
automation services
bots
infrastructure tools
Can Vestauth work without curl?
Yes.
Vestauth provides libraries and primitives that can be integrated into any HTTP client or framework. The CLI simply makes it easy to adopt and demonstrate.
Do I need to run a Vestauth server?
No.
Vestauth is primarily a client-side and verification library. Agents generate keys locally and sign requests directly. Tools verify requests using public keys exposed via .well-known discovery endpoints.
There is no central authentication server required.
Can I host my own Vestauth server?
Yes.
To host your own Vestauth server create the database, run the migrations, and start the server.
$ vestauth server db:create$ vestauth server db:migrate$ vestauth server startvestauth server listening on http://localhost:3000
Why does Vestauth use Ed25519 keys?
Ed25519 provides:
Strong modern cryptographic security
Fast signing and verification
Small key sizes
Wide ecosystem support
How does Vestauth authentication work?
Vestauth uses HTTP Message Signatures (RFC 9421). Each request is signed using the agent's private key. The request includes signed headers such as:
Signature
Signature-Input
Signature-Agent
Tools verify the request by retrieving the agent's public key from a discovery endpoint and verifying the signature cryptographically.
If the signature is valid, the tool knows the request was created by the agent that owns that private key.
How does Vestauth prevent replay attacks?
Vestauth prevents replay attacks using multiple mechanisms built into HTTP Message Signatures.
Each signed request includes:
created timestamp - limits how old a signature can be
expires timestamp - defines a short validity window
nonce value - ensures each request is unique
Tools verify that:
The signature is still within the allowed time window
The nonce has not been used before
The signature cryptographically matches the request
Because signatures are short-lived and tied to unique nonce values, an intercepted request cannot be reused successfully.
Tools may optionally store nonce values for additional replay protection.
Why does Vestauth use public key discovery?
Public key discovery allows tools to verify agent signatures without manual key exchange. Each agent hosts its public keys in a standardized .well-known directory.
This enables dynamic agent onboarding while preserving cryptographic verification.
Does Vestauth send secrets over the network?
No.
Vestauth signs requests using private keys locally. Only public keys are shared for verification.
How does Vestauth avoid SSRF during public key discovery?
Vestauth prevents Server-Side Request Forgery (SSRF) by restricting public key discovery to trusted domains.
By default, Vestauth only resolves agent discovery endpoints inside the controlled namespace:
*.api.vestauth.com
When a tool verifies a request, Vestauth converts the agent identity into a fixed .well-known endpoint within this trusted domain. Because this domain is controlled by Vestauth, tools never fetch attacker-supplied URLs or internal network addresses.
This removes the most common SSRF attack vector during signature verification.
Custom trusted discovery domains
Tools can optionally configure additional trusted discovery domains using:
Only discovery endpoints matching this allowlist will be fetched.
Defense in depth
Why does Vestauth use .well-known discovery instead of embedding public keys directly?
Vestauth uses .well-known discovery to keep requests small, enable key rotation, and support long-term identity management.
Embedding public keys directly in every request would increase header size, reduce caching opportunities, and make key rotation difficult. By publishing keys through a discovery endpoint, Vestauth allows tools to fetch and cache keys independently from individual requests.
This approach provides several benefits:
Efficient requests
Public keys are retrieved once and can be cached by tools. Agents do not need to send large key material with every request.
Key rotation support
Agents can rotate signing keys without changing their identity. Tools simply refresh keys from the discovery endpoint.
Multi-key support
Agents can safely publish multiple active keys (for rotation or staged rollouts) using the standard HTTP Message Signatures directory format.
Standards alignment
Vestauth follows the discovery model used in:
HTTP Message Signatures directories
OAuth / OpenID Connect key discovery
Web identity federation systems
Contributing
You can fork this repo and create pull requests or if you have questions or feedback: