Story protocol · pay to remix

Operate the Story protocol layer behind a 402 toll.

Register IP assets, attach PIL terms, and mint license tokens on demand. Agents pay 0.01 USDC, you return on-chain receipts driven by the official Story SDK.

Built on Base with x402 payment guards. We never custody funds, just orchestrate Story protocol workloads once receipts clear.

View payable actionsCall the Story endpointsRead the whitepaper
/api/story/ip-assets/register•$0.01/api/story/licenses/attach•$0.01/api/story/licenses/mint•$0.01

Story protocol ops, pre-priced and 402-compliant.

Each action exposes a turnkey Story SDK workflow. Agents pay a single Base USDC toll, we return signed transactions and identifiers ready for remix markets.

register-ip
$0.01
POST /api/story/ip-assets/register

Register IP Asset

Register an existing NFT on Story as a programmable IP asset with optional metadata so downstream agents can build on it.

Request payload

  • nftContract (0x-address) — ERC-721 contract address that already exists on Story-ready chains.
  • tokenId (string) — Token identifier to register as programmable IP.
  • ipMetadataURI (string) · optional — URI pointing at the IP metadata JSON (optional but recommended).
  • ipMetadataHash (0x-hash) · optional — Keccak256 hash of the IP metadata payload.
  • nftMetadataURI (string) · optional — URI for the NFT metadata (will be mirrored into the IP record).
  • nftMetadataHash (0x-hash) · optional — Keccak256 hash of the NFT metadata payload.
  • deadline (number) · optional — Optional signature deadline in seconds (defaults to 1000).

What you get back

Returns Story transaction details including tx hash, IP ID, and token ID so agents can link the asset across chains.

attach-license
$0.01
POST /api/story/licenses/attach

Attach PIL Terms

Attach pre-registered Programmable IP License (PIL) terms to a Story IP so other agents know how they can remix it.

Request payload

  • ipId (0x-address) — Story IP identifier (the IP smart account address).
  • licenseTermsId (number) — Numeric ID of the registered PIL terms to attach.
  • licenseTemplate (0x-address) · optional — Optional template contract address if you use a non-default template.

What you get back

Returns the attachment transaction hash and an acknowledgment that the license is now live on-chain.

mint-license
$0.01
POST /api/story/licenses/mint

Mint License Tokens

Mint license tokens for a licensed Story IP so downstream agents can capture commercial rights and revenue splits programmatically.

Request payload

  • licensorIpId (0x-address) — IP ID that granted the license terms.
  • licenseTermsId (number) — License terms identifier used for minting tokens.
  • amount (number) · optional — Number of license tokens to mint (defaults to 1).
  • receiver (0x-address) · optional — Wallet that will receive the newly minted license tokens (defaults to Story service wallet).
  • maxMintingFee (string) · optional — Upper bound you are willing to pay for the minting fee (0 means no limit).
  • maxRevenueShare (number) · optional — Maximum revenue share percentage you accept for the license token mint operation.

What you get back

Returns minted license token IDs, transaction hash, and receipt references so agents can custody the rights they paid for.

x402 story pipe

Push programmable IP without leaving your paywall.

We keep the Story SDK behind a 402. You keep clean receipts for every IP registration, license attachment, and token mint your agents demand.

01

Select a Story action

Agents hit /api/story/actions, grab the SDK play they need, and preview required parameters alongside output guarantees.

02

Swipe 0.01 USDC

x402 paymentMiddleware enforces Base mainnet receipts. No license tokens or IP registrations are executed until the toll clears.

03

Ship on-chain receipts

We invoke the Story SDK server-side and respond with tx hashes, IP IDs, and license token identifiers ready for downstream automations.