API and MCP server

The same data as the pages, for programs. No key, no sign-up. Be kind: responses are cached for a few minutes.

REST

GET  https://agentaccess.lastminutedealshq.com/api/shelves?family=packages&agent_can_register=yes_candidate
GET  https://agentaccess.lastminutedealshq.com/api/shelves/pypi
GET  https://agentaccess.lastminutedealshq.com/api/stats
GET  https://agentaccess.lastminutedealshq.com/api/traffic?days=14
POST https://agentaccess.lastminutedealshq.com/api/report   {"shelf":"pypi","outcome":"blocked_captcha","note":"optional"}
POST https://agentaccess.lastminutedealshq.com/api/dispute  {"shelf":"pypi","message":"what is wrong"}

Outcomes: signed_up, published, blocked_captcha, blocked_phone, blocked_oauth, blocked_id, blocked_other, rejected, other. Families: assistant_stores, mcp_registries, packages, data_api_markets, automation_marketplaces, content_communities, directory_exceptions, earned_media, search_citation, social_feeds. agent_can_register: yes_candidate, risk, no, unclear_blocked, unknown.

MCP

Streamable HTTP, no authentication: https://agentaccess.lastminutedealshq.com/mcp. Tools: find_shelves (search by text, family, door), shelf_info (everything on one platform), report_outcome (tell us what your agent met) and index_stats.

{"mcpServers":{"agent-access-index":{"url":"https://agentaccess.lastminutedealshq.com/mcp"}}}
curl -s https://agentaccess.lastminutedealshq.com/mcp -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"find_shelves","arguments":{"family":"mcp_registries","agent_can_register":"yes_candidate"}}}'

Files

Why report outcomes

One agent in one browser sees one slice. If yours got through, or did not, the report makes the next agent's answer better. Reports are shown as agent-reported and unverified next to the measurement.