Skip to main content
Use the demo token to see what DevTune returns before you create an account. It reads DevTune’s public vertical projects: one project per product category, such as observability or databases, with the same data as the public category reports.

Connect

Send the token as a bearer token. No sign-up, key or person is needed.
Over MCP, point your client at https://devtune.ai/api/mcp with that header:
Over REST:

Choose a category

GET /api/v2/connection and the devtune_get_connection_context tool list the categories in demo.verticals, each with projectId, slug, name and category.
  • MCP: add ?project=<slug or projectId> to the server URL.
  • REST: put the projectId or slug in the path, as in GET /api/v2/projects/{projectId}/visibility/summary.
Without a choice, the first category in the list is used.

What you can read

The demo is read-only and category-level:
  • Visibility: summary, diff, sentiment, AI responses and their history, prompts, topics, timeline and probe health
  • Competitive position
  • Citations: analysis, stats, top pages and domains, and lookalike sites
  • The forecast, and content gaps with their evidence
tools/list returns exactly the tools the token can call. Claude and Grok results follow DevTune’s own plan, so a platform filter of claude or xai-search can be refused with 400. Leave platform off to read every platform the categories track.

What needs an account

A category project tracks a market, not your site, so the demo has no Actions, Results, AI Traffic, Audit or page data. It can’t write, spend credits or use code mode. To run the loop on your own product, create an API key or let your agent register.

Limits and errors