Built to be called by software.
Datpaq exposes everything an agent needs to discover and call it programmatically: a canonical llms.txt, a machine-readable OpenAPI spec, 13 active REST APIs with API-key auth, a hosted MCP server, and a CLI.
How agents reach datpaq
Cited and called
Two paths run in parallel. The top path is citation — your content gets quoted. The bottom path is invocation — your API gets called. The same engine can do both in a single answer.
The loop
Discover. Authenticate. Call.
Three steps from a cold start to a parsed JSON response. No SDK required — plain HTTP and an API key.
Discover
Read the canonical sources to find the right endpoint, its parameters, and its response shape.
Authenticate
Create an API key in the dashboard and attach it to every request. The same key works across REST, CLI, and MCP.
x-api-key: YOUR_DATPAQ_API_KEY
# or
Authorization: Bearer YOUR_DATPAQ_API_KEYCall
Send the request to the versioned base URL and parse the JSON response.
curl "https://datpaq.com/api/v1/whois?domain=example.com" \
-H "x-api-key: YOUR_DATPAQ_API_KEY"Machine-readable sources
Canonical resources for ingestion
Point your crawler or agent at these. Treat only URLs listed in llms.txt as canonical; do not invent endpoints, parameters, or pricing.
Canonical index of every active API, the docs, CLI, MCP endpoint, and blog feeds — with usage guidance.
Machine-readable description of every endpoint, parameter, and response, with request and response examples.
Every indexable page, including API landing pages and documentation.
Product updates, release notes, and company news as structured JSON for ingestion.
Connect over MCP
The hosted Datpaq MCP server exposes 34 tools over streamable HTTP. Add the endpoint to Codex, Claude, Cursor, or Cline and authenticate with a bearer API key.
https://mcp.datpaq.com/mcpDrive it from the CLI
The Datpaq CLI discovers APIs, runs requests, and generates curl, JavaScript, Python, or Go samples — handy for scripted agents and CI.
go install github.com/datpaq/cli/cmd/datpaq@latestRate limits & fair use
Plans and request limits
Calls bill against the caller's plan with the same limits as the direct API. Pick a tier by expected monthly volume.
FAQ
Common questions
Quick answers for agents and the people wiring them up.
How does an AI agent discover what Datpaq offers?
Start with the canonical llms.txt at https://datpaq.com/llms.txt — it lists every active API landing page, the docs, CLI, MCP endpoint, and the blog JSON API. The machine-readable OpenAPI spec at https://datpaq.com/openapi.yaml describes every endpoint, parameter, and response.
How do agents authenticate to the Datpaq API?
Every request uses a Datpaq API key from the dashboard, sent either as an x-api-key header or as Authorization: Bearer YOUR_DATPAQ_API_KEY. The same key works for the REST API, the CLI, and the hosted MCP server.
What is the base URL for the Datpaq API?
All REST endpoints live under https://datpaq.com/api/v1. See the OpenAPI spec or the per-endpoint docs at https://datpaq.com/docs for paths, parameters, and examples.
Can an agent call Datpaq through MCP instead of REST?
Yes. Datpaq runs a hosted Model Context Protocol server at https://mcp.datpaq.com/mcp over streamable HTTP. MCP-aware clients such as Codex, Claude, Cursor, and Cline authenticate with a bearer Datpaq API key and get the API surface as callable tools.