API Explorer
Let developers try real API requests from inside the app.
What it adds
An in-app request builder that runs calls against your API and shows the exact request and response.
What your agent is told to do
6
What your agent is told to do
6-
1
Generate the request form from the API's own schema so parameters, types, and required fields cannot drift from the real endpoints.
-
2
Execute calls through a server-side proxy that attaches credentials, so a key is never placed in browser-visible code or the network tab.
-
3
Restrict the proxy to your own documented API endpoints only. An explorer that will call an arbitrary URL is an SSRF hole with a nice UI.
-
4
Run requests with the current user's real permissions and show endpoints they cannot call as denied rather than hiding them — a silent omission reads as a missing feature.
-
5
Mark unsafe methods clearly and confirm before sending. A POST from a documentation page still creates real data.
-
6
Do NOT store request or response bodies in history without redacting authorization headers, tokens, and any field the API marks sensitive.
Edge cases it handles
6
Edge cases it handles
6- Copyable curl and code samples must contain a placeholder, never the live credential the proxy used.
- Very large responses will freeze the browser if rendered whole. Truncate with a way to download the full body.
- Requests must time out and be cancellable, or a slow endpoint hangs the panel indefinitely.
- Explorer traffic counts against rate limits. Label it distinctly so a developer can tell exploration from production usage.
- The explorer must follow the API version the account is pinned to, and say which version it is calling.
- Where the API has a sandbox or test mode, default the explorer to it and make switching to live an explicit, obvious act.
Definition of done
8
Definition of done
8- The request form is generated from the API schema, not hand-maintained.
- Credentials are attached server-side and never exposed to the browser.
- Only documented first-party endpoints are reachable through the proxy.
- Permission-denied endpoints are shown as denied rather than omitted.
- Stored history has authorization headers and sensitive fields redacted.
- Generated code samples use credential placeholders.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
AI Cost Budgets
AI Cost Budgets
Cap what AI features are allowed to spend before the bill arrives.
What it does
Monetary spending limits on AI work, scoped by workspace, feature, and time period, enforced before a run starts.
How it works
- 1 Find every place the app calls a model and route all of them through one accounting point that records estimated and actual spend against a scope. A budget that only covers the chat feature is not a budget.
- 2 Estimate the cost of a run from the size of its input before dispatching it, and refuse anything that would exceed the remaining budget on its own.
- 3 Reserve the estimate against the budget when the run starts, then reconcile to the real usage figures when it finishes, releasing whatever was over-reserved.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-cost-budgets
Multi-Model Routing
Multi-Model Routing
Send each AI request to the right model using rules you can read and test.
What it does
A deterministic routing layer that picks a model per request from task type, context size, latency budget, and data sensitivity.
How it works
- 1 Express routing as explicit, ordered rules over inputs the app can measure: task type, estimated context size, latency budget, and the sensitivity classification of the data involved. A rule set that can be read line by line can be reviewed and tested.
- 2 Make routing deterministic. The same inputs must always produce the same route, so a bad output can be reproduced and a rule change can be evaluated. Randomised or load-based selection turns every incident into guesswork.
- 3 Classify data before routing and refuse to route restricted content to any destination not approved for it. This check is a hard block, not a preference, and it must run before the request is assembled.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/multi-model-routing
SEO Setup
SEO Setup
Make your app findable — titles, meta, Open Graph, sitemap, robots.
What it does
The baseline SEO and social-preview setup every public app should have, and most skip.
How it works
- 1 Give every public page a unique, descriptive title and meta description. Find the app's layout and add a mechanism for each page to set them.
- 2 Add Open Graph and Twitter Card tags so shared links render a preview instead of a bare URL.
- 3 Generate a sitemap.xml covering every public, indexable page, and a robots.txt pointing at it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/seo-setup
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.