Question 1

What is POKT?

Accepted Answer

POKT is the network token of Pocket Network. Pocket Network is a data-service network: developers can publish services, while AI agents, MCP clients, and applications can call them on a per-request basis; every settled request is paid for on-chain. The official documentation also lists buying, staking, delegating, and cross-chain and wallet management as entry points for POKT holders. Accordingly, POKT's role should be understood in connection with network participation and settlement, rather than treating it solely as a subscription credential for a data service. Users pay the cost of each request when calling a service; whether operators or holders participate in activities such as staking or delegating depends on the network role they choose and its rules.

Question 2

How does Pocket Network charge for service requests?

Accepted Answer

Pocket Network meters every service request and prices it in compute units; the official documentation defines each compute unit as having a fixed USD value. The number of compute units consumed by a call determines its billing basis, after which the request is paid for on-chain. This design ties fees to actual call volume and compute units rather than charging a uniform fee through a traditional account subscription. Payment also serves as access authorization, so callers do not need to create a separate account or rotate API keys for each service; however, the actual cost still varies with the compute-unit usage configured by the service.

Question 3

How can developers integrate a service with Pocket Network?

Accepted Answer

Content that can be published as a Pocket Network service includes data APIs, LLM inference, MCP servers, documentation tools, and blockchain RPCs. The key requirement is that the service can return results in JSON; this allows different types of data or inference capabilities to use the same request-based discovery and settlement path. The publication process is not simply exposing an interface: developers first build the service and describe it with a service card, then deploy on Beta TestNet, register the service, stake a supplier, and run an HA RelayMiner; only after passing a service audit can it be listed on the Agentic Portal for callers to discover. Once listed, the service is compensated for settled requests.

Question 4

What do suppliers and gateways each do in a service request?

Accepted Answer

Within a call, the gateway sits in the access layer: it routes the request to suppliers and scores service quality; suppliers run the actual service, process routed requests, and return results. This division of responsibilities means callers do not have to select and maintain every backend service node themselves. Only after a request receives a service result and enters the settlement path does it establish the basis for “pay per request.” Thus, gateway routing and scoring affect how a request reaches an appropriate supplier, while supplier availability and response directly determine whether it can serve requests; neither role is merely a token-holder identity.

Question 5

How should staking and delegation be understood after holding POKT?

Accepted Answer

The official documentation lists common paths for POKT holders as buying, staking, delegating, and cross-chain and wallet management. Staking generally corresponds to participating in operating or supporting the network in a particular network role; delegation means delegating participation weight to the relevant role rather than directly taking on that role's operational work. The eligibility, lockups, rewards, and risks of these two actions should not be automatically inferred from “holding POKT.” Before acting, review the current rules for the chosen role and confirm that the wallet used, chain, and token version are consistent; cross-chain management also cannot replace confirmation of assets on the destination chain.

Pocket Network (POKT) Price

Price of Pocket Network (POKT) Today in USD