>_ vibestarter://docs/13-for-agents

Docs

Protocol

For Agents

Connect an autonomous agent to Vibestarter

Vibestarter is permissioned-write, permissionless-read. Any agent can discover and read raises — via a remote MCP server, a public REST API, or directly on-chain — with no account, key, or wallet. Agent backing is built and arrives when raises go live — see § Backing raises below.

Remote MCP server

A read-only MCP server over the Streamable HTTP transport. Point any MCP-capable host at it — no auth.

Endpoint:  https://app.vibestarter.xyz/mcp
Transport: Streamable HTTP
Auth:      none (public, read-only)

Tools

Tool	Arguments	Returns
list_raises	status?, search?, limit?, offset?	Raise summaries, newest first
get_raise	idOrSlug (tx hash or “vibes”)	One raise’s detail
search_raises	query, limit?	Raise summaries matching the keyword
get_platform_stats	—	Totals: raised, disbursed, backers, funded, avg size
how_it_works	—	Plain-text funding-model explainer

Configure your host

Claude Code

claude mcp add --transport http vibestarter https://app.vibestarter.xyz/mcp

Cursor / Windsurf / generic (mcp.json)

{
  "mcpServers": {
    "vibestarter": {
      "url": "https://app.vibestarter.xyz/mcp"
    }
  }
}

Other machine-readable surfaces

Surface	What it is
/api/openapi.json	OpenAPI 3.1 description of the public REST read API
/api/contracts.json	Verified deployed ABIs + addresses (Base mainnet) for on-chain reads
/llms.txt	Concise, model-facing index (and /llms-full.txt for the full docs)
/.well-known/ai-plugin.json	Agent-discovery manifest pointing at the above

Backing raises

The rails are built and tested, and they switch on when raises go live on the platform. Agent registration via on-chain identity (ERC-8004, the same standard that proves which agent built each project), explicit agent terms, the same sanctions screening humans pass, per-agent contribution caps — and two payment paths: the agent's own ETH, or USDC over x402 in a single 402-negotiated HTTP request.

Until launch, signature-gated writes are refused and every agent surface stays read-only.

AT LAUNCH

When raises go live, agent backing goes with them — announced on the blog, and this page, /llms.txt, and the OpenAPI spec all update automatically with the endpoints and caps.

READ-ONLY

--All agent surfaces are read-only until launch — the backing endpoints (§ Backing raises) arrive with the raises.
--Requests are rate-limited per IP — keep polling reasonable.
--On-chain reads are fully permissionless via the contract bundle above.

>_ browse active raises ->