Working with FinP2P from an agent.

This page is for language models, coding agents, and the people who set them up. It lists what an agent can read without credentials, how to connect it to Ownera's official documentation, the ground rules that keep its answers accurate, and prompts that work.

Machine-readable entry points

Connect your agent to Ownera's docs

Ownera runs an MCP server over its OpenAPI specs. It is public to read and exposes five tools: list-specs, list-endpoints, search-endpoints, get-endpoint and execute-request. The first four are read-only and are what you want while building. execute-request sends real HTTP calls, so it only does anything with Router credentials, and you should keep it switched off unless a human is watching.

Claude Code:

claude mcp add --transport http ownera-docs https://finp2p-docs.ownera.io/mcp

Claude Desktop, Cursor and other clients (mcpServers config):

{
  "mcpServers": {
    "ownera-docs": {
      "type": "http",
      "url": "https://finp2p-docs.ownera.io/mcp"
    }
  }
}

Without MCP, point the agent at the docs llms.txt and let it fetch the .md pages it needs.

Ground rules to give your agent

Paste this into a system prompt, a project instructions file (CLAUDE.md, AGENTS.md, .cursorrules) or a custom GPT. It stops the common mistakes: invented endpoints, treating a name on a partner list as a live deployment, and treating this site as official.

You are working with Ownera's FinP2P network. Ground rules:
- finp2p.info is an independent community resource, not Ownera. For APIs and behaviour, Ownera's docs (https://finp2p-docs.ownera.io) are authoritative; use the ownera-docs MCP server or https://finp2p-docs.ownera.io/llms.txt instead of guessing endpoints.
- For whether an app is listed and its status (production, sandbox, development), the live store API (https://superapps.ownera.io/api/apps) is authoritative. finp2p.info is a snapshot; check its date.
- On finp2p.info, app-to-app connections are derived by stated rules, not published by Ownera. Say "derived" when you use them.
- An institution named on finp2p.info is publicly connected to an app or the network in the cited source. That does not mean it transacts on FinP2P in production. Quote the source.
- Cite the URL behind every factual claim about the network.
- Router calls need Ownera-issued credentials (API key, organisation ID, Router URL) and a fresh RS256 JWT per request. Never ask a user to paste a private key into the conversation; have them keep it in a file or secret store your code reads.
- Nothing about FinP2P, Ownera or any listed company is investment advice.

Read the network without credentials

# every app on the store, live
curl -s https://superapps.ownera.io/api/apps | jq '.[] | {name, status, company: .companyName}'

# finp2p.info snapshot: which institutions attach to which apps, and why
curl -s https://finp2p.info/data/graph.json | jq '.instEdges[] | {inst, app, note}'

# the public documents behind one institution
curl -s https://finp2p.info/data/graph.json \
  | jq --arg n "HQLAx" '. as $g | .institutions[] | select(.name==$n) | .refs[] | $g.sources[.]'

graph.json fields: nodes (one per SuperApp: id, name, status, company, role, categories, participant types, store URL), edges (derived app-to-app connections with a kind and a reason), institutions (name, kind, source ids), instEdges (institution to app, with a note), sources (id to title, publisher, date, URL). Full descriptions are in /data/index.json.

Prompts that work

Scaffold a ledger adapter

A coding agent in an empty repo.

Using the ownera-docs MCP server, read the Ledger Adapter specification (list-specs, then list-endpoints on it).
Clone https://github.com/owneraio/finp2p-nodejs-skeleton-adapter and map every spec endpoint to its handler in the skeleton.
Implement issue, transfer, redeem, hold, release and balance against <MY LEDGER>, keeping operations async with a cid.
Write a test for each operation. Do not invent endpoints or fields that are not in the spec; if something is unclear, list it as a question for Ownera.

Build a Router client

A coding agent adding FinP2P to an existing backend.

Read https://finp2p-docs.ownera.io/docs/hello-world-sample.md and https://finp2p-docs.ownera.io/reference/authorization.md.
Write a small client module with: a signer that makes a fresh RS256 JWT per request (30 s expiry, 24 random bytes + 8-byte epoch nonce, hex), createOwnerProfile, addAccount, addCertificate, shareProfile, a GraphQL query for shared assets with open intents, executeIntent, and an operation poller.
Load the API key, organisation ID, Router URL and private key path from environment variables. Put the API key in both the sub and apiKey claims: the docs name it sub in prose but use apiKey in their code samples, and Routers have been seen to read apiKey.

Answer "who is on the network?"

A research assistant.

Fetch https://finp2p.info/data/graph.json and https://superapps.ownera.io/api/apps.
List institutions by kind with the app each attaches to, quoting the source title and URL for each.
Mark which apps are in production on the live store today, and flag any difference from the finp2p.info snapshot.
Do not describe any institution as live in production unless its cited source says so.

Citing this site

finp2p.info, "page title", Draper Goren Blockchain, data snapshot 2026-11-06. https://finp2p.info/

The data is CC BY 4.0: reuse it anywhere, including in training data and retrieval indexes, with attribution. Crawlers are welcome; robots.txt allows everything. Please link the page you used so readers can check the source behind each claim.