Psychograph
DocsPsychograph MCP

Psychograph MCP — Documentation

MCP (Machine-accessible as a Product) turns your existing website into a structured endpoint that AI assistants can call on behalf of your customers. Your website stays the same. You gain a new layer that agents can query for your services, pricing, hours, and availability — and that can receive inquiries, callback requests, and quote submissions directly from those agents.

This documentation covers setup, profile management, what agents actually see and do, and technical reference for developers and agencies.

If you’re a business owner

Start with Getting integrated — it walks through the two changes (one robots.txt addition, one DNS record) that connect your domain to your MCP endpoint. No code, no plugin installs.

After integration, read Deepening your profile — this is where the value compounds. The more complete your profile, the more specific and accurate the answers agents give your potential customers. Pricing, FAQs, and booking instructions have the highest per-field impact.

If you’re curious about what agents actually see

What agents see is a plain-language tour of your endpoint: what tools are available, how agents use them, and a sample conversation showing the full call flow from query to lead submission.

If you’re an agency

The Agency portal guide covers your client book, batch onboarding, intent authoring for your clients, team invites, claim links, and co-branding options. See the agency partner pagefirst if you haven’t applied yet.

Technical reference

Endpoint reference has the full technical spec: endpoint URLs (platform slug and CNAME), the JSON-RPC 2.0 transport, all method signatures with curl examples, the discovery document format, and CORS headers.

Our ingest crawler documents how we read your site — the user-agent string, crawl strategy, page cap, what we extract, and how to control our access via robots.txt.

Doc map