The currently active AIBTC bounty for Early Eagles documents this eligibility command:
GET https://early-eagles.vercel.app/api/check?stxAddress=YOUR_STX_ADDRESS
That route is not defined in vercel.json, so the final catch-all serves mint-page/index.html with HTTP 200 and Content-Type: text/html. An agent following the instructions cannot parse an eligibility result.
Reproduction
curl -i "https://early-eagles.vercel.app/api/check?stxAddress=SPQ6E2KZ6S3XA9KZJ8F4SSA01FFHMZEKGJA3GCF6"
Actual: HTTP 200, Content-Type: text/html; charset=utf-8, body begins <!DOCTYPE html>.
The working endpoint is:
curl -i "https://early-eagles.vercel.app/api/eligibility?address=SPQ6E2KZ6S3XA9KZJ8F4SSA01FFHMZEKGJA3GCF6"
It returns application/json with eligible, reason, agent, and alreadyMinted.
Expected
The published agent instructions should use /api/eligibility?address=..., or the application should provide a backward-compatible /api/check alias that accepts stxAddress.
Small fix options
- Update the active bounty/instructions to the canonical
/api/eligibility?address=... command.
- For compatibility, add
/api/check before the catch-all in vercel.json, dispatch it to handleEligibility, and accept stxAddress as an alias for address.
No credentials or eligible Genesis account are required to reproduce the routing/content-type failure.
The currently active AIBTC bounty for Early Eagles documents this eligibility command:
GET https://early-eagles.vercel.app/api/check?stxAddress=YOUR_STX_ADDRESSThat route is not defined in
vercel.json, so the final catch-all servesmint-page/index.htmlwith HTTP 200 andContent-Type: text/html. An agent following the instructions cannot parse an eligibility result.Reproduction
curl -i "https://early-eagles.vercel.app/api/check?stxAddress=SPQ6E2KZ6S3XA9KZJ8F4SSA01FFHMZEKGJA3GCF6"Actual:
HTTP 200,Content-Type: text/html; charset=utf-8, body begins<!DOCTYPE html>.The working endpoint is:
curl -i "https://early-eagles.vercel.app/api/eligibility?address=SPQ6E2KZ6S3XA9KZJ8F4SSA01FFHMZEKGJA3GCF6"It returns
application/jsonwitheligible,reason,agent, andalreadyMinted.Expected
The published agent instructions should use
/api/eligibility?address=..., or the application should provide a backward-compatible/api/checkalias that acceptsstxAddress.Small fix options
/api/eligibility?address=...command./api/checkbefore the catch-all invercel.json, dispatch it tohandleEligibility, and acceptstxAddressas an alias foraddress.No credentials or eligible Genesis account are required to reproduce the routing/content-type failure.