Meet the Prezenti Season 3 AI Builder Sponsorship Cohort

Ecosystem Grants
1

Prezenti’s four-month AI Builder Sponsorship trial is now fully subscribed. Five builders have accepted their places and recorded their commitments publicly on Celo.

The cohort will receive up to $7,000 in combined support. Each builder can receive up to $1,400 across four months: Claude Max 20x reimbursement up to $200 per month, ChatGPT Pro 5x reimbursement up to $100 per month, and a $200 flexible allowance across the term.

The cohort

Bureau - Afolabi Emmanuel

Africa | Payments
GitHub | X: @Spagero71

Bureau is an autonomous FX desk on Celo. It monitors Mento stablecoin price drift, acts on market opportunities, and makes market data available through x402.

AbaPay - Oluwafemi Olagoke

Africa | Payments
GitHub | X: @investorphem

AbaPay is extending its Celo agent-payment rails, using stablecoins and x402 to connect autonomous payments with practical services such as utilities, airtime, data, and settlement.

GoodDrops - Oshioke Salaki

Africa | Payments
GitHub | X: @oshioke_salaki

GoodDrops is a live, location-based treasure hunt and merchant utility on Celo. People hide and discover GoodDollar rewards at physical locations, while merchants can participate through GoodSpots.

Blokaz - Onanike Samuel Chisom

Africa | AI
GitHub | X: @oxeagleeyes

Through Cracked Studios, Samuel will use the sponsored AI tooling to expand Blokaz and accelerate the design, development, and release of further Celo products.

Kali Decoder - Neeraj Choubisa

Asia | Payments
GitHub | X: @itsNikku876

Neeraj will build an open-source, privacy-preserving payment application on Celo for simple, low-cost stablecoin transfers, with clear payment history and documented architecture.

Monthly progress updates

This thread is the canonical public record for the cohort. Each sponsored builder must post one reply per sponsorship month, no later than the end of that month. Please use this format:

Month [1-4] - [Project name]

Summary
What changed this month in two or three sentences.

What shipped
The product, engineering, research, or distribution work completed.

Evidence
Links to deployments, repositories, pull requests, documentation, transactions, attestations, usage dashboards, or other verifiable work.

Usage and feedback
User activity, partner or user feedback, lessons learned, and any measurable outcomes.

Celo progress
What is live on Celo, what was integrated, and what remains.

Blockers
Anything slowing delivery or requiring an introduction.

Next month
The concrete work planned for the next sponsorship month.

Continued support for months three and four requires a verifiable Celo mainnet deployment, integration, or material ecosystem contribution by the end of month two. Thirty days without qualifying activity triggers a review and a seven-day opportunity to provide evidence or explain an interruption.

Receipts and personal billing information must not be posted here. Builders should send monthly reimbursement receipts privately to admin@prezenti.xyz and redact card or billing details.

Public commitments

Each builder has recorded the accepted goodwill pledge in the public Celo pledge ledger. The pledge covers 2% of defined Celo revenue and relevant grant, prize, or retro-funding income, is capped at $14,000, expires 36 months after the sponsorship term, and is pro-rated if fewer than four months of sponsorship are received. Builders retain their IP and equity and may withdraw without penalty.

We welcome technical feedback, integration ideas, distribution support, and introductions for the five builders. Follow their progress in the replies below.

6 Likes
2 
## Month 1 - AbaPay

### Summary
AbaPay is a set of payment rails that lets AI agents pay real bills (airtime, data, electricity, cable TV, exam PINs) from their own Celo wallet in USDC, USD₮ or USA₮, over x402, MCP and A2A. This month we focused on making the rails easy for outside agents to adopt:
- an SDK release,
- an open-source reference agent,
- Self Agent ID on every agent rail,
- AbaPay's own on-chain identities.

### What shipped
- **Self Agent ID on MCP, A2A and x402.** Agents can sign requests with their Self Agent ID, and AbaPay checks them against the SelfAgentRegistry. Verified agents are shown as verified on every response and recorded with the payment. A signature that doesn't check out is refused with 401. An expired or revoked agent still pays, but shows as unverified.
- **AbaPay registered as Self agent #196,** backed by a passport proof (no personal data disclosed) and owned by the same wallet as our ERC-8004 identity #9687.
- **abapay-sdk 0.5.0 (npm) and 0.3.1 (PyPI):**
  - Self Agent ID signing.
  - A `confirm` hook that lets an agent cap its spend before anything is signed.
  - Data, cable and exam plans over x402.
  - A Celo-first quickstart.
  - A fix: earlier versions paid in USDC even when USD₮ was requested.
- **Open-source reference agent (MIT).** Clone it, fund a Celo wallet with about $1, and pay a real bill in under 10 minutes. It has a spending cap and an optional plain-English mode.
- **x402 fix for Node.js agents.** Our 402 price header had grown to about 22 KB, over Node's 16 KB limit, so Node clients couldn't read the price. It's about 6.8 KB now.
- **Electricity fix.** Postpaid meters paid over x402 (including from MiniPay) were wrongly refunded. The meter type is now read correctly.i

### Evidence
- Self agent #196 registration tx: https://celoscan.io/tx/0x31cd31f264e25c6128af9b4eff63cd74c5b5d348d3633856c2dee371bf6b75a4
- ERC-8004 #9687: https://8004scan.io/agents/celo/9687. Its registration file links our Self Agent ID page: https://abapays.com/.well-known/agent.json
- Self Agent ID docs: https://docs.abapays.com/start-here/self-agent-id
- Reference agent: https://github.com/investorphem/abapay-reference-agent
- SDK: https://www.npmjs.com/package/abapay-sdk
- Pull requests: https://github.com/investorphem/AbaPay/pull/168 (Self Agent ID), /169 (report), /170 (SDK), /171 (Node fix), /172 (docs), /174 (Self #196), /175 (alert fix), /176 (meter fix)
- Celo x402 vault: https://celoscan.io/address/0x5df8aE2B963165b735B18Ca86B1ea448d2AA032C
- Live on-chain stats: https://stats.abapays.com
- Intro post: https://forum.celo.org/t/abapay-payment-rails-for-ai-agents-to-pay-real-bills-on-celo-x402-mcp-a2a/13936

### Usage and feedback
- **Payments:** this month's payments on Celo came from AbaPay's own web app users , independent agents and our testing.
- **Bugs found through our own use:** testing surfaced the Node header bug and the postpaid meter bug, both now fixed.
- **Listings:** AbaPay is live on the official MCP Registry, Glama, awesome-mcp-servers, 8004scan and cursor.directory. Listings on awesome-x402, awesome-agentic-commerce and awesome-remote-mcp-servers are pending review.

### Celo progress
- All agent rails default to Celo, with USDC, USD₮ and USA₮.
- x402 settles through the Celo facilitator into our Celo vault.
- AbaPay holds ERC-8004 #9687 and Self agent #196 on Celo mainnet.


### Next month
- Onboard new independent agents and developers through the reference agent, and publish their transactions.
- Get at least one outside agent with a Self Agent ID paying through AbaPay.
- increase number of transactions
- Post progress updates on X and run a live builder session.
1 Like
3

Month 1: Remesso

Summary

This month, Remesso went from a consumer app for recurring stablecoin payments to payment infrastructure for apps and AI agents on Celo. Two contracts are live on mainnet: RemessoExecutorV5 for scheduled payments and RemessoAgentAllowance for the on-chain spending caps a person sets for their agent. remesso-sdk 0.3.0 is on npm with agent-to-agent payments, payment events, webhooks, and full documentation. Usage is still our own, and first outside integrations are the goal for month two.

What shipped
Contracts on Celo mainnet, both verified: RemessoExecutorV5 (16 Oct), which every new schedule runs on, with fixes from automated security scans; and RemessoAgentAllowance (19 Oct), where a person caps what their agent may spend per payment and per day, with an expiry and an optional recipient list. It has no owner and no admin.

remesso-sdk on npm: 0.1.0 and 0.2.0 (25 Oct), and 0.3.0 (26 Oct), covering:

  • recurring schedules;

  • agent payments that pay once per idempotency key;

  • one-off agent-to-agent payments, from the agent’s wallet or from a spending policy;

  • payment requests and signed invoices;

  • payment events and signed webhooks;

  • payment verification from the chain alone;

  • Postgres for several workers sharing one key;

  • a local fork environment (npx remesso-sdk dev).

    Receiving payments (25 Oct): an indexer that records every payment from the chain, matching of payments to requests, and webhook delivery (Standard Webhooks) with retries.

    Wallets for AI agents:

    • the Remesso wallet, an MCP server for Claude Code, Codex and Cursor that pays only within an on-chain policy (npm remesso-wallet, now 0.6.1);

    • a Claude connector at remesso.xyz/mcp;

    • x402 v2 paid endpoints for live peso and real rates and routes, which the official x402 client can pay.

      Builder codes (ERC-8021, 25 Oct): an integrator’s code rides on every payment of the schedules it creates, so Celo credits that volume to the integrator.

    • Documentation:

      • docs.remesso.xyz has guides, six worked use cases, and an API reference, and every code example is type-checked against the SDK.
      • Build with AI (26 Oct) publishes the same pages as llms.txt, llms-full.txt, and a remesso-sdk skill for coding assistants.

  • Tokens and wallets:

    • Ripio wARS, wBRL, and wCOP (6 Oct), USA₮ (11 Oct), and cNGN (14 Oct), paid out in the same token they’re funded in;
    • in MiniPay, paying someone by phone number (11 Oct).

  • Testing:

    • Two independent code reviews before release found 28 issues our own tests had missed, including ways a retry could pay twice. Each is fixed with a regression test, and the SDK has 186 tests.
    • We ran end-to-end tests on mainnet, including the first wallet-funded agent-to-agent payment (26 Oct).

Evidence

Usage and feedback

  • On-chain since mainnet launch (22 Sep): 21 schedules and 27 scheduled payments, delivering USDT, USDC, USA₮, cNGN, and wARS. Since 19 Oct, 16 agent spending policies and 12 agent payments. All of it came from our own team’s wallets while we built and tested. We don’t have an outside integrator yet.
  • npm, 1–26 Oct: 535 downloads of remesso-sdk (first published 25 Oct) and 375 of remesso-wallet. These include mirrors and our own installs, so we don’t count them as users.
  • Feedback: Reviewers told us the repository read as a consumer remittance app, the plan had no budget or milestones, and there was no usage from outside our team. This month’s work answers the first point. Outside usage is the goal for month two.
  • Lessons:
    • Celo’s public RPC spreads calls across nodes, so a read just after a write can come from a node a block behind. Our mainnet runs hit this on 25 and 26 Oct, and the SDK now retries those reads.
    • Independent reviews caught what our own tests missed, so every release now gets one before publishing.

Celo progress

  • Live on Celo mainnet:
    • RemessoExecutorV5 and RemessoAgentAllowance;
    • gas paid in stablecoins through fee abstraction;
    • x402 endpoints settled by Celo’s facilitator in USDC and USA₮;
    • an ERC-8004 identity (agent 9879, held by the wallet that sends every payment), with Self Agent ID 191;
    • ERC-8021 attribution on every transaction, plus integrators’ builder codes;
    • MiniPay phone number payments through ODIS;
    • Ripio wFIAT and cNGN, paid out in the same token;
    • Naira cash-out through a link to Textile.
  • What remains:
    • outside integrations;
    • a testnet or sandbox, so a developer’s first payment costs nothing;
    • Schedule discovery that keeps up with many one-off payments;
    • Celo’s x402 facilitator writing builder codes on settlements (x402-rs/x402-rs#99).
    • Naira bank payouts stay off pending legal advice.

**Blockers

Integrators:** introductions to Celo teams building agents or payment apps who could integrate remesso-sdk.

Next month

  • First outside integrations: three teams paying or getting paid through remesso-sdk on mainnet, visible on-chain through their builder codes.
  • Security: start an audit of both contracts, or open a public bug bounty if an audit can’t start yet.
  • A free first payment: a testnet deployment or hosted sandbox.
  • Scaling: schedule discovery from the event index, so one-off payments scale.