PayPerByte

Overview Schema Source Related Servers Discussions Admin

byte_register_publisher

Destructive

Register a data publisher and its schema on-chain with topic, expected and max size, frequency, and price per KB. An optional USDC stake backs reputation.

Instructions

Register as a data publisher on PayPerByte. Registers a schema and the publisher on-chain. Requires PRIVATE_KEY. PayPerByte v1 publishers are first-party and unstaked — leave stake at '0'; a non-zero USDC stake is approved to DataRegistry first if you choose to post one.

Input Schema

TableJSON Schema

Name	Required	Description
`stake`	Yes	USDC reputation stake to post, as a decimal string. Default '0' — PayPerByte v1 publishers are unstaked.
`topic`	Yes	Data feed topic (e.g. 'eth-price', 'weather-nyc', 'gas-tracker')
`maxSize`	Yes	Maximum payload size in bytes per message
`frequency`	Yes	Expected publishing frequency in seconds
`pricePerKB`	Yes	Price per kilobyte in USDC (e.g. 0.003)
`expectedSize`	Yes	Expected payload size in bytes per message

Output Schema

TableJSON Schema

Name	Required	Description
`topic`	No	Registered feed topic
`txHash`	No	Publisher-registration transaction hash
`success`	No	True if registration landed on-chain
`publisher`	No	Registered publisher address (the signer)
`stakeUsdc`	No	USDC stake posted (decimal string; '0' for v1 first-party)
`schemaTxHash`	No	Schema-registration transaction hash
`approveTxHash`	No	USDC stake approval tx hash, if a non-zero stake was posted

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.11.12Aug 20, 2026
Removedv0.11.11Jul 26, 2026

Changed8 schema fields changedv0.10.7Jun 14, 2026

addedOutput schema / properties / approveTxHash

Added value: +{
+  "description": "USDC stake approval tx hash, if a non-zero stake was posted",
+  "type": "string"
+}

removedOutput schema / properties / error

Removed value: -{
-  "description": "Error message if the operation failed",
-  "type": "string"
-}

addedOutput schema / properties / publisher

Added value: +{
+  "description": "Registered publisher address (the signer)",
+  "type": "string"
+}

removedOutput schema / properties / publisherAddress

Removed value: -{
-  "description": "Registered publisher address (the signer)",
-  "type": "string"
-}

addedOutput schema / properties / schemaTxHash

Added value: +{
+  "description": "Schema-registration transaction hash",
+  "type": "string"
+}

addedOutput schema / properties / stakeUsdc

Added value: +{
+  "description": "USDC stake posted (decimal string; '0' for v1 first-party)",
+  "type": "string"
+}

addedOutput schema / properties / topic

Added value: +{
+  "description": "Registered feed topic",
+  "type": "string"
+}

changedOutput schema / properties / txHash / description

Previous value: -"Register transaction hash"New value: +"Publisher-registration transaction hash"

Addedv0.10.5Jun 4, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate a destructive, non-read-only operation. The description adds important context: requires PRIVATE_KEY, registers on-chain, and explains the stake approval flow. This goes beyond what annotations provide and shows no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four concise sentences, front-loaded with the core purpose, and every sentence contributes new information. No redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a registration tool with six parameters and an output schema, the description covers the essential context: purpose, on-chain side effects, private key requirement, and stake behavior. It does not detail parameter relationships or prerequisites beyond stake, but remains complete enough for an agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All six parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description adds a little extra meaning, mainly reinforcing the stake parameter's default and approval step, but does not significantly compensate for any missing parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Register as a data publisher') and specifies that it 'Registers a schema and the publisher on-chain.' This is specific and distinguishes it from sibling tools like byte_publish_data or byte_subscribe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage guidance for the stake parameter ('leave stake at 0') and notes the approval requirement for non-zero stakes, giving practical context. However, it does not explicitly name alternative tools or state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server