Agent→Apple docs→You→App Store Connect→Agent→Retry
Copy state back and forth. Explain Apple's screens. Spend context rediscovering the workflow. Still wonder whether the final state is right.
APP STORE TOOLS FOR YOUR AI CODING AGENT
The app works.
The store is another job.
AiSCent gives Claude Code, Codex, Cursor, ChatGPT, and compatible MCP clients structured App Store tools. Start with a free App Store Check to see what is left. Pro prepares supported fixes, keeps important changes confirmation-gated, and rereads App Store Connect to verify what Apple received.
No Apple credentials needed for the check. When you connect AiSCent, do the release work in the coding conversation you already use.
✓App platformmacOS detected
✓Locale folders39 found
!Image comparison4 duplicate groups
→Upload actionWithheld for review
What this preventsA green file count hiding the wrong store story
THE PART AFTER THE BUILDCreators describe the hidden work in their own words.
“The App Store Connect IAP workflow is genuinely confusing the first time.”First-time app maker, shipping story on Reddit ↗
“spending more time on screenshots than on actual development.”Independent developer, screenshot localization story on Reddit ↗
THE APP WORKS. THE STORE IS ANOTHER JOB.
You thought you were done because the code was done.
Then Apple asks for a product page, screenshots, localized storefronts, purchase metadata, subscription relationships, review information, privacy details, and a submission state that actually agrees with all of it.
Store storyScreenshotsLocalizationMetadataIn-app purchasesSubscriptionsReview requirementsSubmission state
PROOF FROM THE REAL MCP WORKFLOW
A complete folder can still be the wrong storefront.
On AiSCent’s own Mac listing, all 39 language folders looked complete—but the same four screenshots were copied into every market. The MCP caught it and stopped the upload recommendation.
This finding came from a direct AiSCent MCP dogfood run. It is product evidence, not a customer testimonial.
READINESSNeeds review
Locale folders39 checked
Duplicate image groups4 flagged
Upload actionWithheld
Same image bytes across different language and script groupsWHY NOT JUST PROMPT YOUR AGENT HARDER?
Your agent isn't missing intelligence.
It's missing App Store-specific tools and state.
You→Agent + AiSCent→Apple
- Inspect actual state
- Prepare the missing work
- Show you the plan
- Make approved changes
- Reread and verify
WHAT YOU'RE ACTUALLY PAYING FOR
Don't become an App Store specialist just because you made an app.
Make the storefront sell the product.
Turn raw product screens and product context into a coherent App Store story instead of treating screenshots like documentation.
Screenshot workflow →Take the story to every market.
Keep metadata and creative together as the message moves across storefronts, languages, and layouts.
Localization workflow →Know what isn't finished.
Surface release gaps across the listing, StoreKit, review information, and App Store Connect before you call the release ready.
Submission readiness →AUTONOMY WITHOUT BLIND TRUST
Your agent works.
You stay in control.
Important work should not disappear behind a green check. AiSCent is built around visible state, deliberate changes, and verification after the change.
01SEERead the real state
02PLANShow what needs to happen
03APPROVEYou decide important changes
04CHANGEAgent performs the work
05VERIFYReread what Apple received
PROOF FROM A REAL AISCENT RELEASE WORKFLOW
AiSCent cleared its own 1.1 submission.
39locale folders checked
156image files compared
4duplicate size groups flagged
0uploads before approval
These numbers describe a verified AiSCent release workflow, not a promise that every app needs the same number of assets or localizations.
TRY ASKING YOUR AGENT
- “Check my app for submission blockers.”
- “Find duplicate screenshots across my locales.”
- “Is my StoreKit config ready for review?”
WHY PAY FOR THIS?
Pay for the part you don't want to become an expert in.
Lowest cash cost. You coordinate Apple docs, App Store Connect, screenshot design, localization, StoreKit metadata, and release state yourself.
Reduce individual jobs, but keep moving product context and assets between your agent, design/localization tools, and Apple.
Human expertise can be excellent, with additional cost and handoffs each time the product or storefront changes.
Keep App Store work with the coding agent that already understands your product, while preserving human approval and verification.
WHY THIS EXISTS
Built by someone who has done this almost 100 times.
I have submitted nearly 100 of my own apps to the App Store, and when Upwork was oDesk, developers paid me to submit theirs. Every check in AiSCent is one I ran by hand. It clears submissions; it does not promise review outcomes.
“I used to sell this work by hand. AiSCent gives your coding agent the App Store tools I wish I had.”Scott Manthey, SMAT Designs
SUBSCRIPTION-FIRST
Your App Store release agent.
Pro includes 2 App Store submission workflows per month, with repairs and resubmissions from those submissions included.
AiSCent connects through an API key you create in App Store Connect (Users and Access → Integrations) and can revoke at any time. It never asks for your Apple ID password.
FREE
$0
Always free. Readiness scan, basic diagnostics, and a limited preview of what needs fixing.
- Full pre-submission scan
- Every issue named and cited
- Nothing sent to Apple
PRO MONTHLY
$11.99 per month
Full App Store preparation: screenshots, localization, StoreKit, submission checks, rejection diagnosis, repairs, and resubmission assistance.
- Everything in the free check
- 2 submission workflows per month
- Repairs and resubmissions included
- Re-verification of each fix
We guarantee our work, not your app. Read the guarantee ↓
PRO ANNUAL
$94.99 per year
Same as monthly, billed annually. Works out to about $7.92/month.
- Everything in Pro monthly
- 2 submission workflows per month
- Upfront annual billing
Our guarantee.
We guarantee our work, not your app. If AiSCent created or prepared something incorrectly, we keep working to correct it at no additional charge. This guarantee covers only AiSCent's preparation work. It does not cover the app's content, behavior, business model, or compliance with Apple's terms, IP issues, account problems, or other things outside AiSCent's work.
BEFORE YOU PAY
The questions we'd ask too.
What is AiSCent?
AiSCent is a macOS setup app and MCP release assistant that gives compatible coding agents structured tools for App Store readiness, metadata, localization, screenshots, StoreKit, and supported App Store Connect actions.
Where does my data go?
Your App Store Connect credentials stay in the macOS Keychain. Supported release operations run from your Mac to Apple through the API key you control. If you choose an optional translation provider, only the text you choose to translate is sent using your own provider key.
Does AiSCent guarantee App Review approval?
No. Apple controls review, and no tool can promise its outcome. We guarantee our preparation work: everything we checked and cleared. If Apple rejects your submission over any of that, we repair it free.
What if Apple rejects my submission anyway?
Bring us the rejection notice within 30 days of its date. If the rejection is over something AiSCent prepared, the repair is included in your Pro subscription. We read what Apple flagged, fix it, re-verify, and you resubmit.
What exactly does the guarantee cover?
Our preparation work, nothing else. If AiSCent prepared something incorrectly, we keep working to correct it at no additional charge. It never covers the app's content, behavior, business model, or compliance with Apple's terms.
Does AiSCent replace Claude, Codex or Cursor?
No. AiSCent extends compatible coding agents with App Store-specific tools and state. You keep working in the agent that already understands your project, while important release changes stay visible and confirmation-gated.
Who is behind AiSCent?
Scott Manthey (SMAT Designs). He has submitted nearly 100 of his own apps to the App Store, and when Upwork was oDesk, developers paid him to submit theirs. He built AiSCent from the rejections he has personally taken.
Is AiSCent a mobile app?
No. It is a macOS setup app and MCP server for preparing App Store releases from iOS app projects.
YOU ALREADY BUILT THE APP.