Farcaster / Base App Integration Rescue

One Farcaster or Base App blocker, fixed in 24 hours.

The free Doctor checks public Farcaster surfaces. A focused repair can also cover one reproducible Base App standard-web, wallet, SIWE, notification, or app-side Base.dev verification blocker.

Open in Farcaster

Free and read-only. No wallet or repository access required.

Need a human fix? See the exact $79 repair scope →

Private, staging, or Base App issue? Request a rescue without a public scan →

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.

ILLUSTRATIVE SCAN — mintboard.example3 blockers · 2 warnings
BLOCKER / IDENTITY

Manifest domain mismatch

accountAssociation is signed for www.mintboard.example, while the app runs on the apex domain.

Likely impact: domain verification and add-app behavior can fail.
BLOCKER / SHARING

Root embed missing

No fc:miniapp metadata was found on the shared URL.

Likely impact: casts render as plain links instead of launchable Mini App cards.
WARNING / RUNTIME

SDK readiness unverified

The public surface cannot prove that sdk.actions.ready() fires in the client.

Next check: run the affected URL inside Farcaster preview.
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.

Seeing “Failed to retrieve debug information”? Follow the manifest debugging guide →

App missing from search? Separate technical blockers from indexing signals →

Images failing validation? Check embed, icon, screenshot, hero, and OG roles separately →

Migrating into Base App? Separate the 2026 standard-web path from Farcaster →

Base.dev verification says “Something went wrong”? Separate project state, the production response, and Base App readiness →

For software agents / x402

Machine-buyable evidence, not another dashboard.

Call either paid endpoint directly. No account or API key; canonical USDC settles on Base before the dossier is released.

Static / fast
$0.75USDC · Base

Static Evidence Dossier

A deterministic snapshot of the public integration surface. It reports exposed manifest, embed, SDK-readiness, and delivery signals without claiming cryptographic or client-runtime verification.

  • Machine-readable JSON dossier
  • Free eligibility check before payment
  • Recovery path for indeterminate settlement
POST/api/x402/miniapp-audit
Pinned / server-side
$5.99USDC · Base

Pinned Server-Side Release Gate

Original-byte JFS verification, fresh finalized Optimism custody and key state, pinned registry-code hashes, strict manifest/embed checks, and bounded PNG byte evidence.

  • GO only queues real-client verification
  • readyForRelease is always false
  • GO requires every referenced image to be PNG
POST/api/x402/miniapp-deep-release

Both products inspect one public HTTPS launch URL. Neither is a security audit, runtime guarantee, or release approval. Never auto-repurchase after an indeterminate result.

Machine manifest →OpenAPI schema →Agent guide →Install agent skill →Add GitHub CI check →
Public evidence / live

Real findings. Open reports. No invented testimonials.

These are public, read-only diagnostics sent to builders who asked for feedback. They demonstrate the evidence format, not completed repairs or customer endorsements.

BRND70

Mini App embedding blocked by response headers

The public app returns X-Frame-Options: SAMEORIGIN and a self-only frame-ancestors policy, preventing third-party client embedding.

Open the public report →
Token Zips98

Manifest still exposes only the legacy key

The live manifest publishes frame but no miniapp entry. The report separates that migration warning from checks that already pass.

Open the public report →
Operator identity and public reply history@tlmnt on Farcaster ↗
Coverage / 01

The narrow layer that makes or breaks distribution.

Farcaster coverage is listed below. Base App repairs are bounded separately to one reproducible standard-web or app-side Base.dev integration blocker.

01

Manifest & identity

Manifest availability and shape, account association, exact domain match, launch URLs, icons, and discovery metadata.

02

Embeds & sharing

fc:miniapp metadata, images, actions, page-specific targets, rich-card rendering, and share flows.

03

Add app & notifications

Saved-app behavior, capability wiring, webhook configuration, events, and the notification delivery path.

04

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.

  1. 01Concise root-cause statement
  2. 02Code or configuration fix in an isolated branch or patch
  3. 03Clean post-fix Doctor scan or documented Base App check
  4. 04Reproduction and verification evidence
  5. 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.

01

Start with evidence

For Farcaster, run the free public Doctor scan. For a Base App blocker, describe the exact failing flow on the request form.

02

Confirm scope

We reproduce the failure and state what must change before requesting any access.

03

Repair

Grant the minimum repository or deployment access needed. We patch one integration failure.

04

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
  • One Farcaster or Base App integration 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.

Request the rescueOr run the free public scan →
NO 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?+

For Farcaster: manifest, embed, launch, notification, SDK, and Mini App-specific mobile failures. For Base App: one bounded standard-web migration, wallet, SIWE, notification, or app-side Base.dev verification blocker. The public scanner itself covers Farcaster surfaces only.

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 Farcaster public checks first. For a Base App blocker, request a scoped reproduction directly. Pay only after the fix is proven.

Base App blocker or no public URL? Request the rescue directly →Free · Read-only · No wallet required