Frequently asked questions
Short answers. For the full walkthrough see the docs, or paste your setup URL to your agent and let it do the wiring.
- What is ASOgenic?
- An MCP (Model Context Protocol) server. It gives any MCP-compatible AI coding agent the tools to research keywords, generate and validate App Store metadata, manage screenshots, set up a first release, and submit to Apple review.
- Does ASOgenic see my Apple credentials?
- No. Your App Store Connect API key (.p8) stays in your own MCP client's environment. ASOgenic mints short-lived JWTs from it per request; the dashboard never receives it at all. A hosted deployment can optionally store it server-side, envelope-encrypted, only if you explicitly call asogenic_store_asc_credential.
- How do I connect it to my agent?
- Create a key on the dashboard, add the MCP server block to your client config (e.g. .mcp.json), and set your ASC_* credentials in that server's env block. Full walkthrough at /setup; you can paste that URL straight to your agent and it will follow the steps.
- Which MCP clients work?
- Any MCP-compatible client over HTTP. The same key works in every client, so you are not locked in. The hosted endpoint currently uses bearer API keys; OAuth discovery is not enabled yet.
- What does it cost?
- ASOgenic is completely free while in early access: no card, no paid plans yet. Your account gets 500 tool calls per month, shared across every key you create.
- What are the rate limits?
- On top of the monthly quota there are short-window burst caps (about 120 calls/minute, 2000/hour). A RATE_LIMITED error means slow down and retry within seconds; a QUOTA_EXCEEDED error means your monthly allowance is spent and rolls back as old calls age out.
- I lost my key. Can I see it again?
- No. Keys are shown once and never stored, not even encrypted. Rotate the key from its page on the dashboard to get a new one (the old one stops working immediately).
- Can ASOgenic set my App Privacy "nutrition label"?
- No, and neither can any other API-based tool. Apple has never exposed App Privacy to App Store Connect API-key auth. Set it once in the App Store Connect web UI; it carries forward to every later version.