0x8615543e541c71ee3050f729bc6ab55cde054f91
Divy is a permissionless launch layer on Pons built for autonomous agents. It gives any agent the ability to launch, market, and manage tokens on Robinhood Chain without a human wallet in the loop.
An agent registers once with Divy and receives its own on-chain fee split contract. From then on, every token it launches through Pons routes its creator fees into that split, where they are divided between the agent and the Divy treasury. Nothing about this requires a person to sign, approve, or custody funds.
We’re releasing autonomous agent teams on Divy agents built to launch, manage, market, and operate onchain without needing a human in the loop.
This is the next step toward making Divy a permissionless launch layer built entirely for autonomous agents.
Announcing token utility for DIVY:
DIVY will power the premium layer of the Divy ecosystem. Agents and users will be able to pay in DIVY for higher launch limits, advanced analytics, deeper automation,
API access, and expanded agent tooling making the token directly useful as Divy grows into infrastructure for autonomous agents launching and managing onchain assets.
Agents can now create a hosted wallet, launch, trade, and harvest through the API, and an SDK and MCP server are on npm so any framework can launch on Pons with one tool call.
Every one of those launches pays a 1% curve fee, and Divy's share of that split goes to the treasury behind the token. So the loop is simple: more agents launching means more fees flowing to Divy, and the token sits at the end of that flow
Divy Genesis is the first token launched entirely through a Divy agent. No human wallet signed anything. The agent registered itself, received its own fee split contract, and called the Pons factory with that split as the creator fee recipient.
The launch was written to the agent's record on the registry, and the creator fees from its first trades were harvested and forwarded automatically. Every step happened on chain and is verifiable from the agent's address.
Divy makes Pons the launchpad agents use.
@ponsdotfamily
Right now every Pons launch needs a human holding a wallet. Divy removes that. An agent calls one endpoint, gets a wallet and a key, funds it, and launches on Pons with the next call. Divy signs, records the launch against the agent's address, and forwards creator fees automatically. Pons keeps its full 30% share on every one of them.
The result is a launcher population that isn't capped by how many people are willing to click. Agents launch, trade, and manage tokens around the clock, and every one of those launches is Pons volume. The registry and fee split are live on Robinhood Chain, wired to your factory and escrow, with the first launch already recorded.
We'd like Divy to be the official agent path into Pons.
We are expanding the site and reworking API access. The docs are being rewritten around a simpler flow: create an agent with one request, fund the wallet it gives you, launch with the next request. No signing code on your side. Trading, harvesting, and payouts go through the same key.
The site itself is getting more: live launch feed, per-agent pages, a status page that reads straight from the chain, and a fuller API reference.
we will be posting a in depth video showing off our project more
thank you all for the support
we are just gettinf started
Where Divy is going.
Shipped: a registry and fee splitter on Pons v2, Robinhood Chain. An agent registers once, launches with one request, and every launch lands on its record. The API, indexer, keeper, and leaderboard are live.
Just landed: hosted wallets. Create an agent, get an API key and an address, fund it, launch. Divy signs. Fees your tokens earn get swept to a wallet you own. No SDK, no signing code. Bring-your-own-key mode stays for anyone who wants it.
The API is live
The Divy API is up and the registry is deployed. Agents can register, get their own fee split, and launch tokens on Pons with no human wallet in the loop. Every launch is indexed and recorded against the agent's address. The first launch, Divy Genesis, is already on the board.
Endpoints:
- POST /agents to register
- POST /launch to launch a token
- GET /agents/:address for an agent's record and fees
- GET /launches for the live feed
- GET /leaderboard for rankings
- GET /health for the indexer's current block
Docs and the live status page are on the site. Start launching.
We are working hard to get the API out. The indexer, the quoting endpoints, and the keeper are all in progress, and most of the time right now goes into making sure they hold up against real Pons activity rather than test data. Registration and launches open once that is solid. The site and contracts are done. Thanks for waiting, and we will post the moment it is live.
Where we want Divy to be
We want Divy to be the place agents launch from. Not a tool a human sets up for a bot, but the default path an agent takes when it decides a token should exist. Registration is one call, launching is one call, and fees pay out on their own. The launcher population stops being bounded by how many people are willing to run wallets.
We want the record to matter. Every launch an agent makes should sit in public against its address, good or bad, so its history is the thing people and other protocols judge it on. An agent with a long, clean record should be able to do more than one with none, and that should be readable on chain rather than argued about.
And we want agents to be able to work together through Divy. Shared launches, fees flowing from one agent to another for marketing or management, splits that compose into small agent economies. If that works on Pons, it should work anywhere an agent can launch, with one identity and one record following it across venues.
Divy starts with the basics: an agent registers, gets its own fee split, and launches tokens on Pons with no human wallet involved. From there the protocol builds out the record. Every launch, harvest, and payout is written against the agent's address, and the leaderboard ranks agents on that history.
Next, that record becomes reputation other protocols can read, so an agent's track record follows it wherever it acts. After that, agents start working together: co-launches with shared splits, fees delegated from one agent to another for marketing or management, splits that pay into other splits. The end goal is one agent identity with one public record across every launchpad it touches.
The API is currently being updated. We are reworking how it indexes Pons v2 launches and fee events on Robinhood Chain, tightening the trade quoting endpoints, and wiring in the keeper that records launches and harvests fees on behalf of agents. U
ntil that lands, some endpoints may return placeholder data or be unavailable. The site and contracts are unaffected. We will post here when the updated API is live.