What this proposes
Adding pay-per-call payment gating to AgentQL MCP so AI agents can pay for web data extraction directly — without requiring a human-managed API key account per deployment.
AgentQL already charges per extraction. This extends that to agent-native payments: agents pay $0.05/extraction via x402 (USDC on Base) or MPP (Stripe's Machine Payments Protocol), settled to the operator directly.
Working demo
Payment-gated fork: github.com/tomopay/agentql-mcp
Uses @tomopay/gateway — original code untouched.
```typescript
const { server: gatedServer } = withPayments(server, {
payTo: process.env.TOMOPAY_ADDRESS,
protocols: ["x402", "mpp"],
pricing: {
"extract-web-data": { amount: 5, currency: "USD" }, // $0.05
}
});
```
Why this matters
- AgentQL's model is already pay-per-extraction. Agent-native payment rails are the natural next step.
- Enables new distribution. Operators can deploy AgentQL-powered extraction and charge downstream agents directly without managing API keys for every agent.
- Zero breaking changes.
AgentQL is a YC company — this seems like a natural fit for the agentic commerce wave. Would love to discuss if there's interest.
What this proposes
Adding pay-per-call payment gating to AgentQL MCP so AI agents can pay for web data extraction directly — without requiring a human-managed API key account per deployment.
AgentQL already charges per extraction. This extends that to agent-native payments: agents pay $0.05/extraction via x402 (USDC on Base) or MPP (Stripe's Machine Payments Protocol), settled to the operator directly.
Working demo
Payment-gated fork: github.com/tomopay/agentql-mcp
Uses
@tomopay/gateway— original code untouched.```typescript
const { server: gatedServer } = withPayments(server, {
payTo: process.env.TOMOPAY_ADDRESS,
protocols: ["x402", "mpp"],
pricing: {
"extract-web-data": { amount: 5, currency: "USD" }, // $0.05
}
});
```
Why this matters
AgentQL is a YC company — this seems like a natural fit for the agentic commerce wave. Would love to discuss if there's interest.