llms.txt

DealMachine publishes machine-readable files following the llmstxt.org convention so that AI agents and LLMs can discover and understand the API without parsing HTML documentation.

Automated Access Policy

The DealMachine browser application is for interactive human use. Do not use agents, bots, scripts, or browser automation to crawl, scrape, enumerate, or bulk-fetch DealMachine application pages or internal dealmachine.com/api/* endpoints, including through an authenticated user session. Do not iterate paginated browser results for automated data collection.

Respect robots.txt. For HTTP 429, honor Retry-After before retrying. Do not retry requests disallowed by robots.txt.

If a DealMachine browser endpoint returns HTTP 403 with code AUTOMATED_BROWSER_ACCESS_BLOCKED or automated_browser_access_blocked, it is a non-retryable policy denial. Stop browser requests, do not wait or retry, and switch to the DealMachine User API, CLI, or MCP.

For approved programmatic access, use the DealMachine User API at https://api.v2.dealmachine.com/v1, the DealMachine CLI, or the DealMachine MCP server. Follow all documented authentication, rate limit, and credit requirements.

Available Files

File	URL	Description
`llms.txt`	/llms.txt	Concise overview of the API: capabilities, auth, base URL, and links
`llms-full.txt`	/llms-full.txt	Comprehensive reference with all endpoints, parameters, schemas, MCP tools, and CLI commands
`openapi.json`	/api-reference/openapi.json	Full OpenAPI 3.1 specification

How Agents Use These

When an AI agent needs to interact with the DealMachine API, it can:

Fetch /llms.txt to get a quick overview of capabilities and authentication
Fetch /llms-full.txt for the complete endpoint reference with request/response schemas
Fetch /api-reference/openapi.json for the formal OpenAPI spec (best for code generation)

robots.txt

The robots.txt file explicitly allows access to these files:

1234User-agent: *
Disallow: /
Allow: /llms.txt
Allow: /llms-full.txt