Encrata publishes an auth.md file at the root of its domain. Your agent reads it to learn how to authenticate with an API key, then calls the API directly - yours to read, parse, and act on.
Declare an intent once. Your agent reads the auth file, authenticates with the user's API key, and runs email lookups from the same source.
> curl https://encrata.com/auth.md
> # agent reads, authenticates, calls
200 OK - agent authenticated via auth.md
The file is the contract. It explains how to get, use, and verify an API key, describes key settings, errors and rate limits, and links to the endpoint documentation. Fetch the documentation you need. The agent asks the user for an API key when one is required.
Each section is structured for machine parsing. The agent reads auth.md once at startup. Local caching is fine - the file changes only on API updates.
> GET /auth.md
# auth.md
You are an AI agent. This file explains how to get an
Encrata API key and use it to call the Encrata API.
## 1. Get a key
Set the key as ENCRATA_API_KEY - never in the chat.
Never ask for the user's password.
## 2. Use the key
Authorization: Bearer enc_****
## 3. Verify the key
GET /api/account/credits - free
## 4. Key facts
## 5. Errors
## 6. Rate limits
## 7. Rules for agents
full file at encrata.com/auth.md - errors, rate limits and agent rules included. Endpoints are listed in the API docs.
Any agent that can fetch a URL and parse markdown can use auth.md. No SDK required, no special integration - just HTTP GET and string parsing.
Claude Code • Cursor • Windsurf • ChatGPT • CrewAI • LangChain • LlamaIndex • Custom agents
Point your agent at encrata.com/auth.md and it handles the rest. No integration guide, no webhook setup, no client library.