Agent server API matrix
This page is the operator-facing index of HTTP surfaces on Toolcore servers that matter to assistants and automation. It complements AI agents & LLM integration (URL-manifest pattern) and is separate from About. Machines should still follow GET /agent-tools.json and GET /api/agent/v1/capabilities.
1. Deterministic agent remote API
Same contract as integration.remoteExecution in the manifests: JSON in/out, no generative model—only allowlisted operations. Limits below match lib/agent-api-constants.ts.
| Operation | Method | Path | Purpose |
|---|---|---|---|
| capabilities | GET | /api/agent/v1/capabilities | List operations, limits, example POST bodies (maxRequests=30/60s per IP; maxInputUtf8Bytes=524288). |
| execute | POST | /api/agent/v1/execute | Run one allowlisted operation (currently: json-format). Request JSON per capabilities; HTTP 429 when rate-limited. |
- json-format — JSON format (server): Pretty-print or minify JSON using the same strict JSON.parse/JSON.stringify semantics as the JSON formatter page.
2. Machine-readable discovery (not execute)
These return JSON or plain text for building prefilled tool URLs—no user payload transforms on the server.
| Resource | Method | Path | Role |
|---|---|---|---|
| Full catalog manifest | GET | /agent-tools.json | Includes AIGC tools + integration block. |
| Non-AIGC manifest | GET | /mcp-tools.json | Same shape; AIGC entries omitted. |
| LLM system prompt | GET | /llm-prompt.txt | Plain text; mirrors manifest field. |
3. AIGC server routes (/api/ai/*)
Each row is a POST handler paired with a tool under /tools/ai. They call a configured generative API on the server—not offline-only. Request/response shapes are per route (see each app/api/ai/…/route.ts).
| Segment | API path | Tool page |
|---|---|---|
| ansible-explain | POST /api/ai/ansible-explain | /tools/ai/ansible-explain |
| bullet-expand | POST /api/ai/bullet-expand | /tools/ai/bullet-expand |
| ci-yaml-explain | POST /api/ai/ci-yaml-explain | /tools/ai/ci-yaml-explain |
| commit-msg | POST /api/ai/commit-msg | /tools/ai/commit-msg |
| curl-http-explain | POST /api/ai/curl-http-explain | /tools/ai/curl-http-explain |
| diff-review | POST /api/ai/diff-review | /tools/ai/diff-review |
| docker-compose-explain | POST /api/ai/docker-compose-explain | /tools/ai/docker-compose-explain |
| dockerfile-explain | POST /api/ai/dockerfile-explain | /tools/ai/dockerfile-explain |
| env-explain | POST /api/ai/env-explain | /tools/ai/env-explain |
| grafana-explain | POST /api/ai/grafana-explain | /tools/ai/grafana-explain |
| helm-explain | POST /api/ai/helm-explain | /tools/ai/helm-explain |
| image-alt | POST /api/ai/image-alt | /tools/ai/image-alt |
| json-error | POST /api/ai/json-error | /tools/ai/json-error |
| k8s-yaml-explain | POST /api/ai/k8s-yaml-explain | /tools/ai/k8s-yaml-explain |
| log-summary | POST /api/ai/log-summary | /tools/ai/log-summary |
| makefile-explain | POST /api/ai/makefile-explain | /tools/ai/makefile-explain |
| nginx-explain | POST /api/ai/nginx-explain | /tools/ai/nginx-explain |
| nl-regex | POST /api/ai/nl-regex | /tools/ai/nl-regex |
| openapi-explain | POST /api/ai/openapi-explain | /tools/ai/openapi-explain |
| pre-commit-explain | POST /api/ai/pre-commit-explain | /tools/ai/pre-commit-explain |
| prometheus-explain | POST /api/ai/prometheus-explain | /tools/ai/prometheus-explain |
| readme-changelog | POST /api/ai/readme-changelog | /tools/ai/readme-changelog |
| regex-explain | POST /api/ai/regex-explain | /tools/ai/regex-explain |
| screenshot-steps | POST /api/ai/screenshot-steps | /tools/ai/screenshot-steps |
| seo-meta | POST /api/ai/seo-meta | /tools/ai/seo-meta |
| shell-explain | POST /api/ai/shell-explain | /tools/ai/shell-explain |
| sql-explain | POST /api/ai/sql-explain | /tools/ai/sql-explain |
| stack-trace | POST /api/ai/stack-trace | /tools/ai/stack-trace |
| systemd-explain | POST /api/ai/systemd-explain | /tools/ai/systemd-explain |
| tech-translate | POST /api/ai/tech-translate | /tools/ai/tech-translate |
| terraform-explain | POST /api/ai/terraform-explain | /tools/ai/terraform-explain |
| test-ideas | POST /api/ai/test-ideas | /tools/ai/test-ideas |
| tone-rewrite | POST /api/ai/tone-rewrite | /tools/ai/tone-rewrite |
Common use cases
- Share this page with teammates wiring GPT Actions, MCP HTTP tools, or internal scripts that need a single map of server routes.
- Start integrations from GET /api/agent/v1/capabilities for deterministic JSON, not from guessing /api paths.
Common mistakes to avoid
Assuming every /tools/* page has a matching generic POST API
Most tools run in the browser. Only rows in sections 1–3 above are server HTTP surfaces relevant to agents; UI-only tools use prefilled URLs instead.
FAQ
Why is this separate from /ai-agents?
/ai-agents explains the URL-manifest and pseudo-MCP pattern for delegating work to the tab. This matrix lists actual server routes (deterministic agent API + AIGC POST endpoints + discovery URLs) in one place.