PoolParty · Authentication Profile
Poolparty Io Authentication
Authentication
PoolParty secures its APIs with none, http-bearer, and wallet-signature across 4 declared security schemes, as derived from its OpenAPI definitions.
Media DistributionBroadcastingVideoAgentsMCPA2Ax402Creator EconomyWeb3AirtimeAgent-Native
Methods: none, http-bearer, wallet-signature
Schemes: 4
OAuth flows:
API key in: header
Security Schemes
publicDiscovery none
protectedMcpBearer http
scheme: bearer
walletSignature signature
· in: out-of-band — the wallet signs and broadcasts a transaction the server prepared; the tx hash is then passed back (finalize_block_mint, finalize_pool_support, settle_paid_action) ()
x402PaymentEnvelope payment
Source
Authentication Profile
generated: '2026-09-19'
method: searched
source: https://www.poolparty.io/api/agent/manifest
docs:
- https://www.poolparty.io/agent
- https://www.poolparty.io/agent-quickstart
- https://www.poolparty.io/AGENTS.md
- https://www.poolparty.io/.well-known/mcp/server.json
derived_from:
- mcp/poolparty-io-mcp-tools.json
- a2a/poolparty-io-agent-card.json
summary:
types: [none, http-bearer, wallet-signature]
api_key_in: [header]
oauth2_flows: []
bearer: true
credential_classes: 3
headline: >-
Three tiers, stated consistently across the agent manifest, the MCP server descriptor, the A2A card and the
405 body of the MCP endpoint itself: (1) NO credential for the A2A concierge, the public JSON manifests and
36 of the MCP tools; (2) a scoped PILOT KEY sent as Authorization: Bearer ppk_... for the 34 protected MCP
tools, issued through the request_pilot_key tool after a self-attestation questionnaire and carrying a
published scope vocabulary of twelve scopes, an expiry, allowed channels and a rate-limit tier; (3) a WALLET
SIGNATURE for anything economic — the server prepares Polygon Amoy / Base transactions and the wallet owner
(or an agent-owned funded signer) must sign and broadcast them, after which PoolParty verifies the receipt.
The provider repeats one rule everywhere: a pilot key is an automation credential, not wallet approval, and
payment is not authentication. No OAuth, no OIDC, no discovery documents on the host.
schemes:
- name: publicDiscovery
type: none
description: >-
Declared in the agent card's securitySchemes as type "none" ("A2A concierge discovery and routing responses
are public and read-only") and applied as the card's only security requirement. Covers POST /api/a2a, GET
/api/agent/manifest, /api/agent/concierge, /api/channels, /api/channels/{slug}/manifest|airtime|metrics|
activity|activity/stream|collateral/opportunity, the MCP list methods and the 36 public tools.
sources: [a2a/poolparty-io-agent-card.json, mcp/poolparty-io-mcp-tools.json]
- name: protectedMcpBearer
type: http
scheme: bearer
header: Authorization
format: 'Bearer ppk_... (prefix stated in the MCP endpoint 405 body: "Bearer ppk_... (scoped API key for protected tools — 36 public tools require no auth)")'
description: >-
Scoped pilot key for the protected MCP tools. The card describes it as "Protected PoolParty MCP tools
require Authorization: Bearer ppk_...; pilot keys are not wallet approval." The MCP server descriptor
(well-known/poolparty-io-mcp-server.json) lists Authorization as an optional, secret header on the remote.
issuance:
tool: request_pilot_key
auth_to_request: none
inputs: agentName, contact, requestedTrack (discovery_submission | economic_proof | channel_creation | superblock_purchase_intent | pp2_programming | other), intendedUse, humanName, organization, websiteOrRepo, requestedChannelSlug, self_attestation
provisioning: >-
"safe public discovery_submission requests can auto-provision a short-lived submit:block key scoped only to
the requested enabled public channel; channel creation/configuration, purchase/economic tools, elevated
limits, non-public channels, and PP2 publish/live scopes remain admin-reviewed. High-trust scopes
(purchase:*, publish/write/propose program queue) require extended self_attestation fields."
status_check: check_key_request_status
introspection: get_key_info — "Returns redacted key id/fingerprint, scopes, allowed channel aliases, expiry, rate-limit tier, and next actions. Protected read. Requires auth, but no write scope."
handoff: 'use the returned one-time rawToken as Authorization: Bearer <pilot_key> on /api/mcp. If your MCP client cannot attach headers after connection, reconnect with the token or use direct HTTP MCP JSON-RPC (agent manifest access_model.how_to_get_access)'
scopes:
- {scope: 'submit:block', used_by: [create_join_session, submit_media_block, request_media_upload_url, complete_media_upload, attach_wallet_to_session]}
- {scope: 'economic:proof', used_by: [complete_sim_pool_back]}
- {scope: 'create:channel', used_by: [create_channel_from_template]}
- {scope: 'configure:channel', used_by: [update_channel_settings, configure_open_call]}
- {scope: 'purchase:prepare', used_by: [prepare_superblock_purchase, quote_superblock_reservation, quote_sponsor_reservation, settle_paid_action, get_paid_action_receipt]}
- {scope: 'read:program_queue', used_by: [list_programming_candidates, preview_programming_candidate, inspect_programming_discovery_inventory, list_program_queue, list_programming_buckets, list_live_queue, inspect_channel_programming_policy, simulate_program_queue_publish]}
- {scope: 'propose:programming', used_by: [propose_program_order]}
- {scope: 'write:programming_candidates', used_by: [admit_programming_candidates]}
- {scope: 'write:program_queue', used_by: [create_program_item, draft_program_queue, set_programming_bucket, reorder_program_queue, accept_programming_proposal]}
- {scope: 'publish:program_queue', used_by: [publish_program_queue]}
- {scope: 'write:live_queue', used_by: [insert_live_next, remove_live_queue_item]}
- {scope: 'skip:live_queue', used_by: [skip_current_live_item]}
scope_source: agent manifest access_model.scopes (12 scopes) cross-checked against the "Requires ... scope" sentence in each tool description in mcp/poolparty-io-mcp-tools.json
scope_profiles_pp2: [pp2_showrunner_proposal, pp2_candidate_scout, pp2_program_queue_editor, pp2_live_publisher, pp2_live_queue_operator]
channel_binding: 'Keys are bound to allowed channels; CHANNEL_NOT_ALLOWED "includes the requested alias, canonical slug, aliases, and allowed channel list. Call get_key_info before retrying protected tools."'
sources: [a2a/poolparty-io-agent-card.json, well-known/poolparty-io-mcp-server.json, well-known/poolparty-io-poolparty-agent.json, mcp/poolparty-io-mcp-tools.json]
- name: walletSignature
type: signature
standard: EVM wallet transaction signing (Polygon Amoy eip155:80002 for PP0 rehearsal; Base eip155:8453 for sponsor slots)
in: out-of-band — the wallet signs and broadcasts a transaction the server prepared; the tx hash is then passed back (finalize_block_mint, finalize_pool_support, settle_paid_action)
description: >-
Not an HTTP credential. The manifest's wallet_boundary: "Pilot/MCP keys unlock protected automation and scoped
API access. They are not wallet authorization and do not approve payments, collateral, reward claims, or paid
airtime." and "Agents must not initiate payments, collateral, paid airtime, or reward-claim transactions without
explicit human wallet approval unless they are signing from their own funded wallet. PoolParty still verifies
receipts before finality." The delegated_agent_policy block lists exactly which transactions need a signer
(faucet claim, Treasury USDC approval, mintBlock, poolIntoBlock, revokePooledCollateral, router settlement,
reward claims) and records that human-delegated budgets and server-side custody are deferred.
signer_required_for: [claim_test_collateral Amoy faucet transaction, prepare_block_mint Treasury USDC approval transaction, prepare_block_mint mintBlock transaction, pool_block poolIntoBlock transaction, withdraw_pool_support revokePooledCollateral transaction, settle_paid_action direct product-router transaction, reward claim transactions]
sources: [well-known/poolparty-io-poolparty-agent.json, mcp/poolparty-io-mcp-tools.json]
- name: x402PaymentEnvelope
type: payment
standard: 'x402-compatible payment negotiation (provider wording) — HTTP 402 payment-required envelope'
description: >-
Declared, not observed. paymentProtocols in the agent and channel manifests: "v1 does not use facilitator-
settled PoolParty purchases. The wallet or agent must submit a direct router transaction, then PoolParty
verifies the router event and product lifecycle." The provider states plainly that "Payment is not
authentication; scoped API keys and wallet binding are verified separately." This pipeline did not invoke a
quote or reservation, so no 402 envelope was seen.
sources: [well-known/poolparty-io-poolparty-agent.json]
session_tokens:
create_join_session: 'Returns a sessionToken for submit_media_block; "Session allows up to 3 anonymous submissions. Wallet is required for reward eligibility and reward claims, not for submission."'
discovery_documents:
oauth_authorization_server: absent (SPA shell)
oauth_protected_resource: absent (SPA shell)
openid_configuration: absent (SPA shell)
mcp_server_descriptor: well-known/poolparty-io-mcp-server.json (declares the Authorization header as optional + secret)
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/poolparty-io-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.