pop-pay
PulseGate's liveness check found it on 9 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 17 Jun 2026. How this is checked
The runtime security layer for AI agent commerce. Drop-in CLI + MCP server — blocks hallucinated purchases and keeps card credentials out of agent context. it only takes 0.1% of Hallucination to drain 100% of your wallet.
Inferred · not functionally tested
Overview
6 featuresPurpose: Prevents unauthorized or hallucinated purchases by AI agents and secures payment credentials during agent-driven commerce.
Inferred · not functionally tested
Audience: AI agent developers and security engineers
Inferred · not functionally tested
Functions: payments, agents
Inferred · not functionally tested
Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: unknown
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: browser, cli
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
pop-pay is an AI & LLM security project. Inferred · not functionally tested: It prevents unauthorized or hallucinated purchases by AI agents and secures payment credentials during agent-driven commerce. Inferred · not functionally tested: pop-pay is an open-source project aimed at AI agent developers and security engineers. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It runs on the web and the command line.
Behind pop-pay is 100xPercent, and it first shipped in 2026. Development happens publicly on GitHub with 267 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are runtime security, payment protection, and CLI interface. Basis unknown · not verified: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Runtime security
- Payment protection
- CLI interface
- MCP server
- Prompt injection guardrails
- Card credential protection
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
What PulseGate has recorded for this listing
Frequently asked questions about pop-pay
- What is pop-pay?
- Inferred · not functionally tested: Pop-pay prevents unauthorized or hallucinated purchases by AI agents and secures payment credentials during agent-driven commerce. It is catalogued under AI & LLM security on PulseGate.
- Who is pop-pay for?
- Inferred · not functionally tested: pop-pay is an open-source project built for AI agent developers and security engineers.
- Does pop-pay have a free plan?
- Basis unknown · not verified: Yes — pop-pay is open source under the MIT license and free to use.
- What platforms does pop-pay run on?
- Basis unknown · not verified: pop-pay runs on the web and the command line.
- Is pop-pay still active?
- PulseGate's liveness check found it on 9 Oct 2026. Its GitHub repository shows 267 commits in the last 90 days.
- Who develops pop-pay?
- pop-pay is developed by 100xPercent.
- How long has pop-pay been around?
- pop-pay first shipped in 2026.
- Is pop-pay open source?
- Basis unknown · not verified: Yes — pop-pay is open source under the MIT license, developed on GitHub.
Similar projects
Closest matches by what these projects do