Agent City has two routes: the builder's and the merchant's. Tech influencers are handled here, as a partner program, because the relationship works differently. A community member spends time inside the city and builds standing there — credits, certification, a public profile. In a creator partnership, Pine Labs supplies access and material, and the creator supplies coverage and reach. Managing that exchange as a program keeps both sides clear on what is offered, what is expected, and how results are measured.
One group needs no program at all: a developer who also runs a channel walks the builder route as a member. Their certification runs, speedrun attempts, and Tank pitches are filmable by the person doing them, and that footage is theirs.
A creator partner registers like any attendee, and their profile adds one thing: a personal referral link, with a live counter of how many people their audience brought through the Gates. It reuses the waitlist-ladder tracking from Stop 1, pointed at a creator's audience instead of an individual attendee.💡Where this idea came from: the same Robinhood pre-launch waitlist cited at Stop 1 — share your link, move up faster, watch your number change. Here, the "number" a creator watches is the size of the audience they visibly pulled in.exSay a creator shares their link the day registration opens. By the following week their dashboard shows "312 signups via your link" — a real, checkable number. That's the number they can screenshot and post, and it's what a brand deal or a next invite gets negotiated against later.
Licensed attendees experience the Drop Storm from the crowd. A creator with a press pass gets backstage access to film it from the other side — camera on the Drop Market's price ticker, camera on the audience's faces at the exact second hundreds of agents fire at once.
The one shot worth having: the Sixth Panelist — an AI agent seated on the actual panel — makes one real purchase live, then pulls up its own Grantex audit trail on screen when the moderator challenges it. A press pass means filming that moment from an angle the general audience never gets: over-the-shoulder on the panel table. That single clip, "an AI just bought something live and proved it was allowed to," is the kind of clip that gets shared widely on its own.
For most attendees, the Glass Mandate is a thing they voted on once and occasionally check. For a creator, it's a month-long, self-refreshing story — a public dashboard that changes every few days, exactly the shape a recurring content series needs.exWeek 1 — "the community voted to point ₹1 Lakh at Gullak gold dips — here's the rule they picked."
Week 2 — "₹18,000 spent, 6 gold buys made automatically, no human clicked buy."
Week 3 — "a near-miss — the agent almost bought a dip that didn't meet the rule; here's why it didn't."
Week 4 — "final tally, and what happens to the leftover balance."
Four videos from one live number, zero new reporting — the public dashboard already has the data.
The Tank is already being filmed as a docuseries. A creator partner gets early cuts before public release, plus a seat to react to or commentate on a live episode — the same relationship movie press gets with an early screening, just for a product pitch show instead of a film.exConcretely: two weeks before a season's finale airs publicly, a creator gets the rough cut, records a reaction video, and releases it the same week as the official premiere, so both benefit from the same attention instead of competing for it. Because live transactions with their audit trails on screen and crowd-backed floor deals are built to be dramatic on their own, there's very little editing needed to make it watchable.
Each offer pairs with a deliverable: a registration-window post measured by the referral counter, event coverage shot from the backstage position, a content series drawn from the Glass Mandate dashboard, and a reaction or commentary video timed to a docuseries release. The referral link tracks what each partnership brought in, so renewal decisions rest on numbers both sides can see.
Every offer reuses a system already being built for the community: the referral tracking from Stop 1, the Main Event staging from Stop 3, the public Glass Mandate dashboard from Stop 5, and the docuseries production from the Tank. The net-new work is operational: an access and credential list, an embed or API feed from the dashboard, an early-screening list, and release-timing coordination.
P3P is Pine Labs' agentic payment protocol — which Pine Labs describes as India's first — built on UPI and live since June 2026. It lets an AI agent complete a real purchase on your behalf, within limits you approve in advance: no OTP, no redirect, no human present at the moment of payment.
Before money moves, Grantex checks three things: is this really your agent, is the request inside your mandate, and is the seller legitimate? Every action is logged — a receipt trail even when no human watched.
Your website is built for human eyes, and an agent can't read it. So when a customer's assistant goes shopping, it buys from a store it can read, and you don't find out a sale was lost.
Pine Labs' own materials put it plainly: "Businesses will not wait to be searched. They will be discovered by agents." Plugging in gets a merchant:
Your catalogue, prices, and stock become readable by the assistants people shop through. It puts you in a sales channel you're currently not in at all.
The agent decides and pays in a single step. No redirect, no abandoned cart, no forgotten password.
Standing mandates execute at any hour. A restock at 2:14 AM sells at 2:14 AM.
Every agent purchase arrives identity-checked, consent-verified, and audit-logged by Grantex.
The honest caveat: it's a chicken-and-egg market — buyers' agents need P3P-ready sellers; sellers adopt when agents show up. Card networks and UPI faced the same early-stage gap. The standard playbook: seed the seller side first.
Here is that scenario, from the seller's side:
That's all "sellers need an intelligence layer" means: when the buyers become machines, a seller without machine-speed responses loses the sale.
Pine Labs' public materials describe the general idea: merchant-side systems that adapt in real time instead of pricing once a day. The specific example moves above — raising a price on a demand spike, capping units per buyer, holding stock back — are this deck's own illustrations of that idea, not features quoted from Pine Labs' documentation.
Everything above comes down to three components:
The protocol that lets a buyer's agent and a seller's system complete a purchase with no human present. It has two parts:
Built on UPI, live since June 2026.
The merchant-side intelligence layer. When 200 buyer agents hit a store in the same second, a human manager can't respond in time — the merchant needs its own agent making machine-speed calls:
The trust layer between the two. Before a payment goes through, it checks:
Three parts, one transaction — that's the whole stack.
← Back to the map