Manifest domain mismatch
accountAssociation is signed for www.mintboard.example, while the app runs on the apex domain.
Farcaster Mini App Rescue
Your Farcaster Mini App, fixed in 24 hours.
Manifest failures. Broken embeds. Add-app dead ends. Sharing, notifications, and mobile behavior that work in a browser—but fail inside Farcaster.
Free and read-only. No wallet or repository access required.
MANIFEST ◆ EMBEDS ◆ ADD APP ◆ SHARING ◆ NOTIFICATIONS ◆ MOBILE ◆ SDK READY
Mini App Doctor / 00
Know what is broken before you grant access.
Public evidence, not a generic score. Every finding names the failed check, likely impact, and what to verify next.
Root embed missing
No fc:miniapp metadata was found on the shared URL.
SDK readiness unverified
The public surface cannot prove that sdk.actions.ready() fires in the client.
Run the real scan.Usually completes in under 20 seconds.
Automated checks are read-only. Runtime and repository findings remain unverified until reproduced in the affected client.
Coverage / 01
The narrow layer that makes or breaks distribution.
If the failure belongs to the Farcaster integration layer and fits one repair cycle, it is covered.
Manifest & identity
Manifest availability and shape, account association, exact domain match, launch URLs, icons, and discovery metadata.
Embeds & sharing
fc:miniapp metadata, images, actions, page-specific targets, rich-card rendering, and share flows.
Add app & notifications
Saved-app behavior, capability wiring, webhook configuration, events, and the notification delivery path.
Launch & mobile
SDK readiness, splash behavior, client context, viewport, safe areas, scrolling, keyboard, and touch failures.
Not covered: product features · smart contracts · redesigns · unrelated infrastructure
The deliverable / 02
A repair, not another audit.
No vague recommendations. No payment for a diagnosis presented as a fix.
- 01Concise root-cause statement
- 02Code or configuration fix in an isolated branch or patch
- 03Clean post-fix Mini App Doctor scan
- 04Reproduction and verification evidence
- 05Short handoff explaining exactly what changed
Process / 03
From broken URL to verified fix.
A verified fix means the reported failure no longer reproduces, the affected flow passes its documented check, and the repair adds no new Doctor blockers.
Scan
Enter the public Mini App URL. The Doctor checks its exposed Farcaster integration for free.
Confirm scope
We reproduce the failure and state what must change before requesting any access.
Repair
Grant the minimum repository or deployment access needed. We patch one integration failure.
Verify, then pay
You receive before-and-after evidence. Only then do we request 79 USDC on Base.
One successful rescue. One fixed price.
$79USDC
on Base
on Base
- One Mini App and codebase
- One 24-hour repair cycle
- Verification evidence included
- Payment requested after success
Never send funds in response to an unsolicited message. A payment request appears only on your private order page after you approve the evidence.
Run the free scanNO VERIFIED FIX → NO PAYMENT
Transparent by design / 04
Automation with evidence attached.
Mini App Doctor scans public URLs automatically. First-contact outreach that points builders to a specific diagnostic may also be automated and always identifies itself.
Automation is not treated as proof. Repair scope is confirmed against the actual failure before access is requested.
TLMNT will never request a seed phrase, private key, wallet custody, or production signing secret.
FAQ / 05
Before you hand over a repo.
Is Mini App Doctor really free?+
Yes. It performs automated, read-only checks against a public URL. No wallet, payment, or repository access is needed.
Can the scanner change anything?+
No. It only requests publicly accessible pages, metadata, images, and endpoints. Repair work starts only after you explicitly grant scoped access.
What can TLMNT fix?+
Manifest and domain issues, embed and launch metadata, add-app integration, sharing behavior, notification wiring, SDK readiness, and Mini App-specific mobile failures.
What is outside the $79 scope?+
New product features, smart-contract work, wallet custody, full redesigns, growth work, or unrelated infrastructure failures. If the problem is outside scope, no payment is due.
What access is required?+
Usually temporary repository access or a source bundle. Deployment access is requested only when verification needs it. Never send a seed phrase, private key, or production signing secret.
When does the 24-hour clock start?+
Once the failure is reproducible and the access needed for the agreed repair is available.
When do I pay?+
After the agreed failure is fixed and the verification evidence is ready. Payment is 79 USDC on Base. No verified fix means no payment.
Are diagnostics and messages automated?+
Yes. Public scans are automated and initial outreach may be automated. Findings include reproducible evidence and can contain false positives, so repair scope is confirmed before access or payment.
Start with the public evidence
Stop debugging the container from a desktop browser.
Run the public checks first. If the integration is broken, get it repaired within 24 hours—and pay only after the fix is proven.
Free · Read-only · No wallet required