I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1

In plain terms. Our own AI key that the AppFolio robot needs to log in is being rejected — can someone check or replace it in Anthropic's console?
The full question, as raised

ANTHROPIC_API_KEY in Vercel prod for appfolio-browser-agent returns 401 'invalid x-api-key' when hit directly (confirmed with a live curl to api.anthropic.com/v1/messages). It's been failing since 2026-10-13 (Sentry JAVASCRIPT-NEXTJS-1HC, 4 events 08:00-08:01 UTC today, plus the playbook's mistake #25 logging the same root cause starting 2026-10-13). Every AppFolio login drive dies on its first act (stagehand.extract) before a password is typed, so ALL AppFolio browser automation (work orders, renewals, vendor/tenant lookups) is blocked across every identity. PR #511/#512 already fixed the SIDE EFFECT (it no longer wrongly escalates the AppFolio credential breaker), but the actual key is still dead — nothing in my reach can mint a new Anthropic API key or change Anthropic console state.

Why, and what was tried
The session raising this recommends: Check console/billing first
a 175-day-old key suddenly 401ing looks more like an intentional revoke/cleanup than a random expiry, so confirming avoids generating a key that gets revoked again
Tried first, unsuccessfully: confirmed root cause live: pulled the prod key from Vercel, curled it straight at Anthropic's Messages API, got 401 invalid x-api-key; checked git history (no recent repo change to key handling, last Vercel env write was 175d ago) and the playbook (mistake #25) which independently timestamps the same failure starting 2026-10-13; searched the open-decisions ledger for an existing block on this and found none

6678655b is parked on this.

Pick an option above, then press Done.
PropFlow Docs