Instant limited key

Sandbox in 60 seconds

Generate a public sandbox-only key, run API probes, and inspect the minimal MCP boundary. This key is deliberately limited to public sandbox endpoints and cannot unlock private operator/admin surfaces.

Copy/paste API demo

TOKEN=$(curl -fsS https://13flow.eu/api/sandbox/key | python3 -c 'import json,sys; print(json.load(sys.stdin)["token"])')
curl -fsS -H "Authorization: Bearer $TOKEN" https://13flow.eu/api/sandbox/v1/status
curl -fsS -H "Authorization: Bearer $TOKEN" https://13flow.eu/api/sandbox/v1/funds
curl -fsS -H "Authorization: Bearer $TOKEN" https://13flow.eu/api/sandbox/v1/mcp-minimum

Minimal MCP demo included

The public sandbox includes this minimum MCP shape only: public discovery and read-only status/product context. It is only a small public integration shape, not a product claim.

curl -fsS https://13flow.eu/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

What it proves

  • Your workflow can fetch a key and call bounded JSON endpoints.
  • Your agent or notebook can keep source, method and quality boundaries visible.
  • MCP discovery is reachable without pretending private MCP tools are public.

What it does not prove

  • No private data entitlement from the public sandbox.
  • No SLA, redistribution right or investment advice.
  • No standalone MCP product plan.