Frequently Asked Questions (FAQ)
What is Pipegate?
Pipegate is a API monetization protocol that uses blockchain technology to enable payments for API usage without traditional API keys. It implements the x402 payment protocol standard for seamless integration.
How does Pipegate work without API keys?
Instead of API keys, Pipegate uses blockchain-based payment proofs. When you make an API call, you include payment information (transaction hash, stream proof, or payment channel proof) that the server verifies on-chain.
What payment methods does Pipegate support?
Pipegate supports three main payment methods:
- One-time payments: Pay per individual API call using transaction hashes
- Payment streams: Continuous payments using Superfluid protocol
- Payment channels: Prepaid credits that can be used across multiple API calls
What is the x402 protocol?
The x402 protocol is an open standard for API payments that Pipegate implements. It provides a unified way to handle different payment types and ensures interoperability across different API providers.
Which blockchains does Pipegate support?
Pipegate supports multiple EVM-compatible blockchains including:
- Ethereum Mainnet
- Polygon
- Arbitrum
- Optimism
- Base
- Avalanche C-Chain
Do I need to pay gas fees for every API call?
No! That's the beauty of Pipegate. Only the initial payment setup requires gas. Individual API calls use payment proofs that don't require additional gas fees.
How much does it cost to use Pipegate?
Pipegate itself doesn't charge platform fees. You only pay:
- The actual API usage costs set by providers
- Minimal blockchain gas fees for payment setup
- Network fees for payment channels/streams
Is Pipegate secure?
Yes, Pipegate uses proven blockchain security:
- All payments are verifiable on-chain
- No central authority controls your funds
- Payment channels use battle-tested smart contracts
- Server verification prevents double-spending
Can I integrate Pipegate with existing APIs?
Absolutely! Pipegate provides:
- TypeScript/JavaScript SDK for client integration
- Rust crate for server integration
- HTTP interceptors that work with any API framework
- Minimal code changes required
What programming languages does Pipegate support?
Currently, Pipegate provides:
- TypeScript/JavaScript: Full client and server SDK
- Rust: Server integration crate
- Python: Coming soon
- Go: Coming soon
How do payment streams work?
Payment streams use the Superfluid protocol to create continuous, real-time payments. You set up a stream rate (e.g., $1/hour) and the API server verifies your stream is active and sufficient for the requested usage.
What happens if my payment channel runs out of funds?
When your payment channel balance gets low:
- API calls will start failing with payment insufficient errors
- You'll need to top up your channel balance
- Or switch to a different payment method temporarily
Can API providers set their own prices?
Yes! API providers have full control over:
- Pricing per API call
- Minimum payment amounts
- Accepted payment methods
- Stream rates and payment channel requirements
Is Pipegate compatible with traditional payment processors?
Pipegate is designed as a blockchain-native alternative to traditional payments. However, providers can offer multiple payment options, allowing users to choose between blockchain payments and traditional methods.
How do I get started as an API consumer?
- Install the Pipegate SDK:
npm install pipegate-sdk
- Choose your preferred payment method
- Set up payment (fund a channel, create a stream, or prepare one-time payments)
- Add the payment interceptor to your API calls
- Start making paid API calls!
How do I get started as an API provider?
- Install the appropriate Pipegate server integration (TypeScript or Rust)
- Configure supported payment methods and pricing
- Add payment verification middleware to your API endpoints
- Deploy your API with Pipegate integration
- Register on the Pipegate hub for discoverability
Where can I find example implementations?
Check out our examples page for:
- Complete client integration examples
- Server implementation samples
- Payment method demonstrations
- Real-world use case implementations
What if I need help or have more questions?
- Read our comprehensive documentation
- Check the GitHub repository for code examples
- Join our community discussions
- Open issues for bug reports or feature requests