PetalsPetalsPetals
How it worksPower MapDocs
Connect
How it worksPower MapDocs
Skip to the document
Documentation
Getting startedOverviewSetting up Petals
The brainOverviewDoctrineA new systemFrom proposal to actionGoing deeperOpen-source leadsOver timeStake behind the networkStart from an addressValueVestingWhat kind of thing it isWhere power livesWho can move money or change rulesWho gets a votemoloch-v3
The data protocolOverviewPetals' protocols: one rule for every formatsnapshot/v1spec/v1interpretation/v1entry/v1entryV2/v1correction/v1claim/v1claim/v2claim/v3claim/v4layer/v1view/v1view/v2seam/v1usage/v1price/v1price/v2mark/v1mark/v2value/v1value/v2proposals/v1proposals/v2
The rendering protocolOverviewContract: the view (view/v2), how data becomes a flower
Connect your agentOverviewConnect Claude CodeConnect a cloud appConnect CodexConnect Hermes
The APIOverviewContract: HTTP API and MCP
Build it with usOverviewContributing
DocsThe API

The API

docs/api/index.md

Draft introduction — waiting for Elco's words.

The HTTP contract is rendered directly from the repository. It records routes, inputs, outputs and authentication. Sections labelled with a later phase retain that qualification.

For an agent connection, start with Connect your agent.

In this section

Contract: HTTP API and MCP
Edit on GitHub
PreviousConnect Hermes
NextContract: HTTP API and MCP
Edit on GitHub