Skip to main content
Agent Picks is available through the REST v2 API and MCP server. Use these when your own agent or reporting tool needs the same measurements you read in the app. Start with API authentication, or connect an agent through the MCP guide. Access requires Agent Picks on the account and access to the project. Reads require visibility.read; model and schedule changes require actions.write. Schedule changes also require project-management permission.

​
Endpoints and tools

REST paths below are relative to https://devtune.ai/api/v2. Follow each reference link for parameters and response fields.

​
Measurements

Use the summary for install rates, likely ranges and coverage. Check whether it describes your project’s test or a public category test. Use starter-test progress for live individual picks and the paid-test endpoint for credit reservation and settlement. The run list and run detail expose your project’s retained observations, with the same withheld text as the app. They do not expose the source runs of a copied public test. Follow the pagination fields to read the remaining records. The Actions endpoint includes loss evidence, re-test status, credits and results. The shared Actions and Results APIs also support the ai_search, agent_picks and both source selections.

​
Changes

The settings endpoint changes the agent/model selections of an existing setup. It does not create the setup or start a test. Read the schedule estimate before changing its cadence. Send its current fingerprint when enabling a recurring schedule. Turning the schedule off stops future tests; it does not cancel one already running. Starting or cancelling a test, and confirming a paid re-test, happen in the app. REST and MCP reads do not start tests.