Skip to content
VENDOR

Early access

Point an agent team at pons.

Access opens in cohorts as each read surface is wired. Requests are prioritised by what people say they would point a mission at, so what you write shapes which surface lands first.

LiveChain Connectors

Request access

Four fields. The one that matters is the last.

Concrete beats general. This is what prioritises the connector order.

Which areas matter most?

Access tiers

Live SystemOpen now

The full mission model, live. Describe an objective, assemble a team, deploy it and read the brief. No account, no request, no waiting.

  • Complete mission lifecycle
  • All seven agent archetypes
  • Five worked mission examples
Chain ConnectorsBy request

Missions resolving against current chain state as each read surface is wired: factory launches, pool state, swap flow and creator history.

  • Read surfaces as they land
  • Every retained claim traced to a read
  • Direct influence over which surface is next
Team WorkspacePhase 04

Shared missions, scheduled monitors and per-member permissions for a whole team.

  • Scheduled missions and block-range diffs
  • Threshold alerts on graduation distance
  • Shared mission library

Access questions

What chain and protocol does VENDOR cover?
pons on Robinhood Chain. Robinhood Chain is an EVM Layer 2 on the Arbitrum Orbit stack, settling to Ethereum, with ETH for gas and chain ID 4663. pons launches fixed-supply tokens into Uniswap V3 pools paired against WETH, with liquidity held by a locker and a published graduation threshold.
Why one chain instead of many?
Because the useful questions are specific. Distance to graduation, wallet breadth behind a pool, holder carry-over between a creator's launches: none of those generalise across venues, and all of them need the exact mechanics of one protocol to be meaningful. Additional venues are a connector problem for later, not a reason to be shallow now.
Does VENDOR ever need my wallet?
No. It holds no keys, signs nothing and constructs no transactions. Everything it reads is public chain state and public contract data, which is all a non-custodial launchpad exposes by design.
What is the walkthrough on the demo page?
A complete worked example, run end to end, so the full shape of a mission and its brief is legible before you point one at your own objective. The protocol mechanics in it come straight from the pons reference.