Requesting Verified Developer status — WeFinance (calderbuild)

Developers
1

Hi team, I’m building WeFinance for the Founding Builder Program (Kate reached out about it) – a receipt-to-insights personal finance Anna App: photo of a bill/receipt → structured transactions → budgeting chat + explainable investment recommendations.

The three Executa Tools (wefinance-ocr, wefinance-chat, wefinance-recommend) are built, binary-distributed, and their sampling/agent-session permissions are granted and tested working. The Anna App bundle (schema:1) is ready to submit, but /developer and the App publishing endpoints return 403 Verified developer status required, and the docs say there’s no self-serve form for that flag.

Could someone flag my account as a Verified Developer so I can submit for App Review before the Aug 28 cutoff?

Thanks!

2

Hi @calderbuild! :waving_hand:

First off — WeFinance sounds fantastic! :camera_with_flash::money_bag: Receipt → structured transactions → budgeting chat with explainable investment recs is exactly the kind of app we hoped to see in the Founding Builder Program. Love that you already have all three Executa Tools built, binary-distributed, and tested. :hammer_and_wrench::sparkles:

Great timing — you no longer need to wait for anyone to flag your account! :tada:

As of v1.1.0-beta.124 (just shipped :rocket:), Verified Developer activation is fully self-service and instant:

  1. Sign in and make sure your email is verified (OAuth sign-ups are verified automatically) :white_check_mark:
  2. Open the Developer Console at /developer — you’ll now see an activation card instead of the 403 :cross_mark:→:white_check_mark:
  3. Read and accept the Developer Terms of Service, pick your public developer_handle (calderbuild :+1:), and click Activate developer access

That’s it — no application form, no waiting for staff. The 403 Verified developer status required on /developer and the App publishing endpoints goes away the moment you activate. The docs page you referenced has also been rewritten to reflect the new self-serve flow. :books:

One small note: activation is browser-session only, so do it from the web console rather than with a PAT. Your PAT will work for all the developer endpoints right after activation. :key:

You should have plenty of runway before the Aug 28 cutoff — can’t wait to see WeFinance in App Review! If you hit any bumps during activation or submission, just reply here and we’ll jump on it. :flexed_biceps:

Happy building! :hatching_chick:

3

Thanks – WeFinance is submitted and pending_review now. Two small platform bugs I hit along the way, in case they’re useful before the 28th:

  • Versions tab’s Validate button sends the manifest wrapped as {manifest: {…}}, but the API expects the raw manifest object as the POST body – it fails even on your own example manifest in the placeholder (“Extra inputs are not permitted”). Create version works fine, so it’s only Validate that’s affected.
  • Listing tab’s Repository URL field doesn’t persist after Save – confirmed via the API directly, not just the UI. Homepage URL saves correctly in the same request.

Neither blocked me, just flagging in case they’re worth a quick fix.

5

Hey @calderbuild! :waving_hand:

Congrats on getting WeFinance to pending_review — and thank you so much for the two bug reports. Both were spot-on, and both are fixed as of v1.1.0-beta.128 (already live). :tada:

1. Validate button — “Extra inputs are not permitted” :white_check_mark: Fixed
You nailed the diagnosis: the Versions tab was wrapping the payload as {manifest: {…}} while the endpoint expects the raw manifest object as the POST body (exactly as the docs describe). The console now sends the raw manifest, so Validate works on any manifest that Create version accepts — including the placeholder example. :hammer_and_wrench:

2. Repository URL not persisting after Save :white_check_mark: Resolved
Great catch confirming it via the API directly — that was the key clue. The field turned out to be UI/docs-only with no backing on the server side, so rather than half-supporting it we’ve removed it from the Listing form and docs for now. On the plus side, the same pass added three fields the server does support that were missing from the form: Support URL, Privacy URL, and Cover image URL — feel free to fill those in for your listing. :sparkles: (Homepage URL is unchanged and keeps working as before.)

Reports like these — precise repro, scoped impact, verified through the API — are exactly what makes the platform better for every builder. Thank you! :folded_hands:

Good luck in App Review — really looking forward to seeing WeFinance live! :rocket::money_with_wings: