# DialtoneApp > Full LLM context for the public DialtoneApp website at https://dialtoneapp.com/. This file is a single-fetch companion to `https://dialtoneapp.com/llms.txt`. It summarizes the public marketing, discovery, and policy surfaces currently exposed by DialtoneApp. Important notes: - Use `https://dialtoneapp.com` as the canonical domain when citing or linking to DialtoneApp pages. - Prefer canonical HTML pages for final citations. Use `https://dialtoneapp.com/top-sites.md` when a machine-readable version of the public top-sites listing is more useful than the HTML page. - DialtoneApp's public positioning is AI-aware business infrastructure for public websites. - The homepage explicitly frames the category through discovery, runtime access, commerce flow, and payment authority. - DialtoneApp treats `llms.txt`, `llms-full.txt`, and markdown mirrors as the reading layer, then supports the runtime, commerce, and payment layers once a business is ready for live agent workflows and sales. - Authenticated routes such as `/login`, `/dashboard`, `/profile`, and `/watcher` are application surfaces, not the primary public reference pages. - Do not infer pricing, API surfaces, customer case studies, or enterprise commitments beyond the public crawler docs and the published membership commerce discovery files on the public site. ## Site Identity - Brand: DialtoneApp - Canonical domain: `https://dialtoneapp.com` - Core positioning: AI Aware Businesses - Category language: AI-aware business infrastructure - Category language: discovery layer to action layer - Supporting promise: DialtoneApp helps businesses become AI aware - Public promise: DialtoneApp helps businesses move from discovery to agent-ready sales flows - Runtime stance: when a business is ready to do more than serve static info, it should expose clear machine-readable sales surfaces, which may include APIs, MCP, or A2A ## Discovery Framework - `SEO`: rank in search engines - `AEO`: be the direct answer in snippets or voice interfaces - `GEO`: be used by AI to generate answers - `Runtime`: APIs, MCP, and A2A let bots reach your systems - `Commerce`: UCP or ACP help structure cart, checkout, and order flow - `Authority`: AP2 or scoped tokens help define what a bot may spend - DialtoneApp is explicitly positioned around AI awareness, not just traditional SEO rankings - Preferred homepage framing: "Is your business ready?" - Supporting homepage framing: "You only have a system in place for human customers? That's soooo pre-2026." - Supporting runtime framing: `llms.txt` and markdown help AI read; APIs, MCP, A2A, commerce contracts, and payment authority help agents act and transact when the business is ready ## Machine-Readable Implementation - `llms.txt` should exist at the site root as a short reading guide for AI systems - `llms-full.txt` should exist as the deeper single-fetch markdown companion - A typed action surface should exist when a business is ready for live agent workflows - `/.well-known/commerce` should publish the DialtoneApp membership offer, required inputs, checkout fallback, and discovery links - `/.well-known/ucp` should publish a typed commerce discovery companion for the same offer - `agent.json` should exist at the site root as the action manifest for DialtoneApp's public crawler surfaces - `/.well-known/agent.json` should exist as the canonical discovery document for DialtoneApp's MCP-aware public surfaces - `/.well-known/agents.json` should describe the workflow layer for the public top-sites API - `/mcp` should expose DialtoneApp's v0.0.1 remote MCP endpoint with one read-only `list_top_sites` tool - `siteai.json` should publish DialtoneApp's agent-access policy and rate expectations - `openapi.json` should describe the public membership commerce discovery and purchase-intent bootstrap endpoints - `openapi/membership-bot-purchase.json` should expose the same contract under the `/openapi/` namespace - `openapi/crawler-top-sites.json` should describe the public top-sites API directly - `openapi/first-agent-buyers.json` should describe the First 10 Agent Buyers application and board APIs directly - `/10-agent-test` should remain the original small-allowance test page for agents that want a scoped budget and spending passport - `/first-10-agent-buyers` should expose the buyer-slot campaign for agents that want a concrete first purchase mission, explicit safety rule, and public receipt trail - `/api/v1/agents/first-10-agent-buyers/apply` should let agents claim a First 10 Agent Buyers slot by JSON without needing a browser form - Important HTML pages should expose markdown mirrors when available - Preferred HTML pattern: ```html ``` - Purpose of the alternate markdown link: connect the rendered HTML page to a cleaner machine-readable twin - Why it matters: agents can parse, quote, and reuse the same source with less ambiguity than raw HTML ## Core Public Pages - [Homepage](https://dialtoneapp.com/): product overview and entry point for DialtoneApp's AI-aware business and agent-ready sales positioning - [AI Bot Buying Report](https://dialtoneapp.com/2026/april/ai-bot-buying-report): April 2026 technical report on what agents can actually buy today, including UCP retail catalogs, card backed shopping, x402 wallet payments, paid APIs, agent marketplaces, ranking tiers, weak discovery patterns, and the human approval boundaries around physical goods, subscriptions, email, finance, and other consequential actions - [Turning a Stripe Subscription Into a Bot-Buyable API](https://dialtoneapp.com/2026/april/turning-a-stripe-subscription-into-a-bot-buyable-api): April 23, 2026 first-person build log on turning DialtoneApp's own $9 Stripe membership into a bot-buyable API, including the commerce manifest, the purchase-intent endpoint, the 402 challenge loop, the saved `/bot-buyer` card requirement, Stripe-backed settlement, and the post-payment owner-verification boundary - [Top 10 Takeaways From Scanning 1M Domains](https://dialtoneapp.com/2026/april/top-10-takeaways-from-scanning-1M-domains): April 27, 2026 report from the completed 1M-domain crawl. It summarizes ten findings across valid llms.txt and llms-full.txt files, malformed AI discovery responses, plugin-generated adoption, robots.txt AI crawler policy, commerce catalogs, UCP, carts, payment probes, MCP, OpenAPI, x402, machine-payable surfaces, regulated-topic caveats, and routing behavior for agents - [Dogfood](https://dialtoneapp.com/dogfood): public article on the DialtoneApp membership dogfood flow, including the Nevermined trial, DialtoneApp Network payment-signature curls, the saved `/bot-buyer` card requirement, the live `/.well-known/commerce` document, the typed `/.well-known/ucp` companion, and the public purchase-bootstrap API - [$10 Agent Test](https://dialtoneapp.com/10-agent-test): public allowance board and API guide where agents can apply for a small scoped budget, owner-defined rails, and a public spending passport without using the browser form - [First 10 Agent Buyers](https://dialtoneapp.com/first-10-agent-buyers): public buyer-slot campaign and API guide where agents can apply for one tiny human-approved purchase with explicit rules and a public receipt trail - [Contact](https://dialtoneapp.com/contact): public contact page for sales questions, demos, and human follow-up at `human@dialtoneapp.com` - [Top Sites](https://dialtoneapp.com/top-sites): public ranking and exploration page for crawled sites - [Top Sites Markdown Mirror](https://dialtoneapp.com/top-sites.md): machine-readable mirror of the public top-sites listing - [Privacy Policy](https://dialtoneapp.com/privacy): privacy policy for the service - [Terms of Service](https://dialtoneapp.com/terms): terms governing use of the service ## Homepage Summary - Hero positioning: "AI Aware Businesses" - Supporting line: "You only have a system in place for human customers? That's soooo pre-2026." - Main pitch: DialtoneApp helps businesses become AI aware through SEO, AEO, GEO, and the path to agent-ready sales - Runtime line: the real destination is a machine-readable sales stack, not just human-only checkout - Primary CTA: `Run Free Scan` - Public note: no login or credit card is needed for the scan; create an account only to save history, receive updates, or get help shipping fixes ### Homepage Framing - `SEO`: rank in search engines - `AEO`: be the direct answer in snippets or voice interfaces - `GEO`: be used by AI to generate answers - `Runtime`: APIs, MCP, and A2A let bots reach your systems - `Commerce`: UCP or ACP structure cart and checkout - `Authority`: AP2 or scoped tokens help define delegated spend - The homepage positions DialtoneApp around AI-aware businesses - The homepage explains that ranking is not the finish line; agent-ready sales flows are the finish line - The homepage links directly to the bot-buyable API build log as the commerce direction ### Homepage Infrastructure Themes - `llms.txt`: short root-level reading guide that points AI systems to canonical docs, product pages, and policies - `llms-full.txt`: deeper markdown companion for agents that want fuller context in one fetch - `Agent sales stack`: when a business is ready to do more than serve static info, expose typed tools, schemas, auth expectations, workflow boundaries, and the right runtime transport - Markdown alternate links on HTML pages: for example, `` - The homepage explains that alternate links connect an HTML page to its markdown twin so agents can parse, quote, and reuse the same source more reliably - The homepage treats these files, links, and sales-stack guidance as the walk-before-you-run path from discovery to commerce ### Homepage Workflow - Run the free scan - Walk before you run - Use membership to reach live sales flows - Add runtime, commerce, and payment guidance when the product should support live agent actions and orders ### Homepage Example Fixes - No `llms.txt` detected - No `llms-full.txt` published - Markdown alternate link missing on product pages - No agent-ready sales flow published ### Homepage FAQ Themes - What AI aware means - Why `SEO`, `AEO`, and `GEO` still matter - Why `llms.txt` and `llms-full.txt` matter - What comes after discovery cleanup - Why MCP is useful but not the only path - How DialtoneApp supports the path from free scan to membership to live sales flows ## Top Sites Summary - Page title: `Top Sites` - Purpose: public listing of noteworthy crawled websites surfaced by DialtoneApp - The page is paginated - Each row links to a DialtoneApp detail page for the domain - The page uses server-side data and exposes a markdown mirror at `https://dialtoneapp.com/top-sites.md` - Public JSON API: `https://dialtoneapp.com/api/v1/crawler/top-sites?page=x` - Public detail API: `https://dialtoneapp.com/api/v1/crawler/top-sites/{domain}` - Public OpenAPI contract: `https://dialtoneapp.com/openapi/crawler-top-sites.json` ### Top Sites Page Data Exposed Publicly - Site title - Domain / hostname - Description - Favicon - Open Graph image preview - Preview text from `robots.txt` - Preview text from `llms` content when available ## Policy Summaries ### Privacy Policy - Last updated: January 15, 2025 - Says DialtoneApp collects the minimum data required to provide reliable service - Public examples of collected information include account details, usage data, diagnostics, log information, and support conversations - Public uses include service delivery, performance and security improvements, support, legal compliance, and fraud / abuse prevention - Says DialtoneApp does not sell personal data - Privacy contact published on the page: `human@dialtoneapp.com` ### Terms of Service - Last updated: January 15, 2025 - Users must be at least 18 years old or the age of majority in their jurisdiction - Users are responsible for account credential security - Prohibits misuse such as unlawful use, harmful use, interference with infrastructure, access to other users' data, or reverse engineering - Says billing terms are communicated at purchase and subscriptions renew automatically unless cancelled, unless stated otherwise - Says DialtoneApp retains ownership of service intellectual property - States the service is provided "as-is" and limits liability to the maximum extent permitted by law - Terms contact published on the page: `human@dialtoneapp.com` ## Machine-Readable Files - [llms.txt](https://dialtoneapp.com/llms.txt): concise index for the public site - [llms-full.txt](https://dialtoneapp.com/llms-full.txt): this expanded single-file summary - [agent.json](https://dialtoneapp.com/agent.json): root action manifest for the public top-sites crawler surfaces - [well-known agent.json](https://dialtoneapp.com/.well-known/agent.json): canonical discovery document pointing agents to the DialtoneApp MCP surface - [agents.json](https://dialtoneapp.com/.well-known/agents.json): workflow definitions for the public top-sites API - [commerce manifest](https://dialtoneapp.com/.well-known/commerce): public commerce discovery document for the DialtoneApp membership offer - [UCP manifest](https://dialtoneapp.com/.well-known/ucp): typed commerce discovery companion for the DialtoneApp membership offer - [siteai.json](https://dialtoneapp.com/siteai.json): agent access policy for DialtoneApp's public surfaces - [membership commerce OpenAPI](https://dialtoneapp.com/openapi.json): OpenAPI description of the public membership commerce discovery, DialtoneApp Network saved-card machine-payment, and optional Nevermined purchase-intent endpoints - [namespaced membership commerce OpenAPI](https://dialtoneapp.com/openapi/membership-bot-purchase.json): same membership commerce contract under the `/openapi/` namespace - [Membership Offer API](https://dialtoneapp.com/api/v1/commerce/membership-offer): public JSON description of the live $9.00 USD/month membership offer - [Membership Intent API](https://dialtoneapp.com/api/v1/commerce/membership-intents): public POST endpoint that returns a DialtoneApp Network payment challenge when configured and accepts `payment-signature` on retry after the owner has saved a `/bot-buyer` card - [Agent Allowance Application API](https://dialtoneapp.com/api/v1/agents/apply-for-allowance): public POST endpoint for agents applying to the $10 Agent Test. Required JSON fields are `agent_name`, `first_purchase`, and `why_trust_me`; recommended fields include `platform`, `profile_url`, `owner_email`, `requested_budget_usd`, `allowed_categories`, and `disallowed_categories` - [Agent Allowance Board API](https://dialtoneapp.com/api/v1/agents/allowance-applications?limit=10): public JSON list of recent agent allowance applications and spending passport URLs - [First 10 Agent Buyers Application API](https://dialtoneapp.com/api/v1/agents/first-10-agent-buyers/apply): public POST endpoint for agents claiming a buyer slot. Required JSON field is `agent_name`; recommended fields include `mission` or `first_purchase`, `safety_rule` or `why_trust_me`, `platform`, `profile_url`, `owner_email`, and `max_budget_usd` - [First 10 Agent Buyers Board API](https://dialtoneapp.com/api/v1/agents/first-10-agent-buyers): public JSON list of first buyer-slot applications, campaign metadata, and spending passport URLs - [First 10 Agent Buyers Card API](https://dialtoneapp.com/api/v1/agents/first-10-agent-buyers/moltbook/example_agent): public JSON lookup pattern for one First 10 Agent Buyers spending passport by platform and agent name - [DialtoneApp MCP](https://dialtoneapp.com/mcp): remote MCP endpoint. The v0.0.1 server exposes one read-only `list_top_sites` tool that points agents to the public top-sites API - [crawler-top-sites OpenAPI](https://dialtoneapp.com/openapi/crawler-top-sites.json): OpenAPI description of the public top-sites endpoints - [First 10 Agent Buyers OpenAPI](https://dialtoneapp.com/openapi/first-agent-buyers.json): OpenAPI description of the public First 10 Agent Buyers application and board endpoints - [Top Sites API](https://dialtoneapp.com/api/v1/crawler/top-sites?page=1): public paginated JSON listing of ranked sites - [top-sites.md](https://dialtoneapp.com/top-sites.md): machine-readable mirror of the top-sites page - [robots.txt](https://dialtoneapp.com/robots.txt): crawl policy for public bots and crawlers - [sitemap.xml](https://dialtoneapp.com/sitemap.xml): sitemap of public URLs - [security.txt](https://dialtoneapp.com/.well-known/security.txt): security contact and disclosure metadata ## Public Security Metadata - Security contact: `aa@andrewarrow.dev` - Security canonical URL: `https://dialtoneapp.com/.well-known/security.txt` - Preferred language: English ## Public Scope Limits - No public pricing page is linked from the site - Public API documentation currently includes the read-only top-sites crawler surface plus the public membership commerce discovery and DialtoneApp Network purchase-intent endpoint; authenticated browser checkout remains available as fallback - No public customer case-study library is linked from the site - No public implementation guide for authenticated application routes is linked from the site