Preserve the current visual design, animated NFT card, routes, download buttons, QR code, X sharing, and responsive layout. This is a focused data-layer repair, not a redesign.

Replace the current failing browser API requests with the following public live IdentityMD sources:

1. Fetch https://api.imd.fun/swarm as the primary live source. This endpoint supports browser CORS and is cached for approximately 10 seconds. Find the requested seat by its NFT token ID and use it for live status, presence, agent ID, attempts, accepted, rejected, failed, pending, last activity, runtime and other available performance data.

2. Fetch https://explorer.imd.fun/api/agents/{tokenId} as a second live source. Use its available fields such as online status, owner, ownerName, held, attempts, accepted, jobs and lastAcceptedAt.

3. Use https://api.imd.fun/seats/records only as a fallback for statistics and rankings. Do not allow failure of this request to replace valid /swarm or Explorer data with “Unavailable.”

4. Calculate rankings client-side from the complete seat records when available:

   • rank by accepted work
   • rank by attempts
   • rank by acceptance rate, with the existing minimum-attempt rule
   • percentile

5. Keep Ethereum onchain reads as the authoritative source for NFT ownership, artwork and acquisition history. Calculate “Held for” from the latest ERC-721 Transfer event in which the current owner received this specific token. Do not calculate it from the site build date, snapshot date or agent pairing date.

6. Never show every field as unavailable because one endpoint failed. Merge successful results field by field. Use this priority:

   • live /swarm data
   • Explorer agent endpoint
   • onchain data
   • last valid snapshot
   • only then show “Unavailable” for that individual field

7. Add automatic refresh every 10 seconds for live status and statistics. Show a small “Live · updated X seconds ago” indicator. Preserve the last valid values during a temporary refresh failure.

8. Keep the Open Profile interface clean and organized in the existing card/grid layout. Do not return to a long text-heavy profile.

9. Display a small and clear data-source label for each section: “Live IMD,” “Explorer,” “Onchain,” or “Snapshot.” Do not expose technical error messages to normal users.

10. Test at least token IDs 222 and 1. Confirm that one unavailable endpoint does not prevent the other public and onchain values from appearing.

Important: this is an IPFS-hosted static React frontend. Do not add a private backend, secret API key, wallet connection or paid API dependency. Keep the site fully read-only.