Push Protocol
Push Protocol (formerly EPNS) is a Web3 communication and Layer 1 blockchain protocol that enables universal applications deployable once and accessible from any chain. Push Chain is the first true Universal Layer 1 blockchain offering 100% EVM compatibility, 4.2k TPS, 1-second native block time, and instant finality. The platform provides a JavaScript/TypeScript SDK (@pushchain/core) that wraps universal signing, cross-chain transaction routing, multichain execution, message signing, smart contract helpers, and utility functions. Developers can send universal transactions from Ethereum, Solana, BNB Chain, Base, and Arbitrum to Push Chain via a single SDK call, with fee abstraction allowing gas payment in any supported token (ETH, SOL, USDC, USDT). Push Chain also offers a testnet faucet (faucet.push.org) delivering 1 PC per address per 6 hours, and a UI Kit for React-based wallet and signer abstraction.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Push Protocol the way a machine reads it — 9 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Push Protocol scores 31.0/100 (thin), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Push Protocol
Each block below is one kind of artifact we hold for Push Protocol. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Push Chain Core SDK
JavaScript/TypeScript SDK (@pushchain/core) for the Push Chain Universal Layer 1 blockchain. Exposes PushChain.initialize(signer, {network}) for client setup, pushChainClient.un...
Push Chain EVM Client
Push Chain is 100% EVM-compatible; developers can initialize standard Ethers v6 or Viem clients against Push Chain RPC endpoints without modifying existing Solidity ABIs, byteco...
Push Chain Contract Helpers (UEAFactory)
On-chain contract helpers deployed at 0x00000000000000000000000000000000000000eA (UEAFactory). getOriginForUEA(address) returns the UniversalAccountId and isUEA flag for any Pus...
Push Chain Testnet Faucet
Public testnet faucet at faucet.push.org for the Push Chain Donut Testnet. Delivers 1 PC (native gas token) per wallet address per 6 hours. Rate-limited and CAPTCHA-gated. Suppo...
Push Chain UI Kit
React UI component library providing PushUniversalWalletProvider and PushUniversalAccountButton for abstracting wallet connection and universal signer creation in web applicatio...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Push Protocol Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Push Protocol Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Push Protocol Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Push Protocol — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/push-protocol · machine-readable index on apis.io