Snaplii's agent payment layer has no LICENSE file and needs a mobile app
Payments are broken for AI agents. Snaplii unlocks real-world commerce with a safe, tokenized payment layer — giving AI agents access to merchant-native payment credits across 500+ brands — while saving users up to 10% per transaction on top of existing deals and promotions.
At a glance
- What is it?
- A tokenized payment layer that lets an agent spend from a prefunded balance through a scoped API key, delivered as a REST API, a Python CLI, an MCP server and a ClawHub skill. It is aimed at Canada and the US, it lists stablecoins beside CAD and USD, and the repository ships without a license.
- Who is it for?
- Read this as a commercial payment product with a published SDK, not as a library to vendor. Four things to settle first.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 12 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- Snaplii-Inc/agent-to-merchant-payments812 ★ · -1
| Repository | 2026-09-11 | 2026-11-21 |
|---|---|---|
| Snaplii-Inc/agent-to-merchant-payments | 813 | 812 |
-1 Stars in the last 71 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The README promises a License section that the tree does not contain
The table of contents ends with a License entry, and the repository is a payment SDK meant to be installed into other people's projects. There is no `LICENSE` file among the top-level entries, and the license recorded for the repository is empty.
The top level is `.github/`, `.gitignore`, `CHANGELOG.md`, `README.md`, `claude-desktop/`, three `clawhub-` directories, `mcp-server/`, `openapi.yaml`, `scripts/`, `skills-lock.json`, `skills/`, `snaplii-cli/` and `tests/`. Nothing in that list grants anything.
For a client library, a CLI and an MCP server, this is the first thing to resolve, because code installed from an index without a license is normally all rights reserved. A commercial product can perfectly well publish an SDK, but the terms need to be in the repository rather than on a web page, and for an integrator the question of what they may ship is a blocker rather than a detail.
An API key can only be generated from the mobile app
The requirements section is three lines: Python 3.10 or later, Git, and the Snaplii Mobile App, which is marked as required to generate your API key.
The Python detail is split. The CLI works on Python 3.9 and later, while the MCP server requires 3.10 or later, so a 3.9 environment can run the terminal path and nothing else. Given that the MCP server is the integration most agent frameworks will reach for, that floor decides which hosts can use it at all.
The mobile app requirement is the harder constraint. Every agent workflow starts with a person adding funds and minting a key on a phone, which means no automated onboarding, no CI-only environment and no way to test an agent integration without a real account and a device in the loop.
CAD, USD, RMB and two stablecoins sit in one list
The multi-currency claim is a short list: CAD, USD, RMB, USDT and USDC, with an and more. The framing is that an agent can operate across markets and payment contexts without forcing a user into one currency.
Fiat and crypto rails are in the same list, and the README does not say how a stablecoin balance is held, whether it is held at all, or what happens to it if a merchant payment fails in the middle of a conversion. The payment architecture described elsewhere is tokenization, which is a card-network idea, so the stablecoin entries are a different mechanism sharing one sentence.
The country table is more concrete. Merchant purchases are available in both Canada and the United States. Bill payments are available for supported billers in Canada and marked not available in the United States. Peer-to-peer transfers are available in both countries, but only to other Snaplii users, which makes them a wallet-to-wallet move rather than a payment to a merchant.
Authorization is a prefunded balance plus a scoped, revocable key
The security story is three steps, and it is the part of the product that is actually specific.
First, set aside funds: you add the amount you want available as Snaplii Cash inside the app. Second, define access: you create an API key carrying the permissions and spending limits the agent's task needs. Third, the agent executes inside that boundary, drawing on Snaplii Cash, and you can revoke the key in the app.
So the exposure being managed is not the card number reaching a model. It is an agent with a key that can spend a bounded amount until you pull it. What the README does not describe is the mechanics underneath: no per-merchant allowlist, no per-transaction approval prompt, no rate limit and no way to see which key did what beyond revoking it. The section on agentic commerce lists the questions a payment layer should answer, including which agent is acting and whether a transaction can be reused, without giving the answers.
The agent path needs three things and degrades to a human
There is an honest conditional in the middle of the README. For a merchant purchase, an agent can understand the intent, navigate the merchant site, select the product, reach checkout, use Snaplii's authorized payment capability and complete the transaction. But that only works when the agent has the required browser capabilities, account access and user authorization.
When those conditions are absent, Snaplii instead gives the agent the payment or exchange information needed for the user to finish the step. So the product has two modes: an agent that drives checkout to completion, and an agent that prepares a handoff. Which one you get depends on capabilities the README describes from the outside rather than configures.
That is worth knowing before you design around it, because the fallback changes the integration shape entirely.
Four entry points, one OpenAPI file, and a skills lock file
Integrations are listed four ways. A REST API reached by direct HTTP calls to `aipayment.snaplii.com/v2/*` for any language or framework. A Python CLI installed with `pip install snaplii-cli`, aimed at terminal agents, scripts and automation. An MCP server over stdio, listed as best for Claude Desktop, OpenClaw, Cursor and VS Code. And an OpenClaw Skill installed with `clawhub install snaplii-a2m-payment`.
The claim that follows is that the layer is model-agnostic: any model that can make HTTP calls or run a CLI can use it, with Claude, ChatGPT, GPT-4, Gemini, LLaMA and Mistral named as examples.
The repository matches that list. `openapi.yaml` sits at the root, so the API contract is machine-readable; `mcp-server/` and `snaplii-cli/` are separate directories for the two main integrations; `claude-desktop/` holds the desktop configuration; and the three `clawhub-` directories, `skills-lock.json` and `skills/` are publishing plumbing for the skill distribution. There is one tag, v0.16.0, whose note reads Secure Vault authentication and OpenAPI.
500+ brands is a description claim, the README says savings vary
The repository description advertises merchant-native payment credits across more than 500 brands and savings of up to 10 percent per transaction on top of existing deals. The README narrows both numbers: 5 to 10 percent additional discounts at supported merchants, delivered through gift-card purchases, eligible offers and cashback.
Then the qualifier that matters: available brands and savings vary by country, brand and current quote, and merchant offers can be combined only where their terms allow. The word quote is doing real work there, since it implies a rate that is looked up rather than a discount that is published.
So there is no fixed discount schedule in this repository, and the headline brand count appears in the description rather than in a table you can check. The rest of the README is in the same register, and it carries one small editing artifact worth knowing about if you compare the two copies of the shopping-step list: the second one reads `S* elect the product or service`.
Editorial conclusion
Read this as a commercial payment product with a published SDK, not as a library to vendor. Four things to settle first. Licensing: there is no LICENSE file at the top level and the license field is empty, so the default position on code you install with `pip install snaplii-cli` or wire into an MCP client is no grant at all, and the README's table of contents promises a License section that is not in what ships. Access: you cannot generate an API key without the Snaplii mobile app, so an automated test environment needs a real account and a device. Geography and rails: merchant purchases work in Canada and the US, bill payments are Canada-only, and USDT and USDC appear in the same currency list as CAD, USD and RMB without the README saying how those balances are held. Scope: the full agent checkout path needs browser capability, account access and user authorization together, and otherwise degrades to handing payment information back to a person. The one release tag is v0.16.0 from 2026-09-23 and the last push was 2026-10-01.
Frequently asked questions
How does Snaplii keep an AI agent away from my credit card?
You set aside an amount as Snaplii Cash in the app and create an API key with the permissions and spending limits the task needs. Agent payments draw from that balance, the underlying card or bank credentials stay with Snaplii, and you can revoke the key in the app.
What do I need installed to use Snaplii from an agent?
Python 3.10 or later for the MCP server, since the CLI alone works on 3.9 and later, plus Git and the Snaplii Mobile App, which is required to generate your API key. The Python CLI itself installs with `pip install snaplii-cli`.
Can Snaplii pay bills in the United States?
No. The country table marks bill payments as available for supported billers in Canada and not available in the United States. Merchant purchases are available in both countries, and peer-to-peer transfers work in both but only between Snaplii users.
Which integrations does the Snaplii agent payment layer ship?
A REST API at `aipayment.snaplii.com/v2/*`, a Python CLI on PyPI, an MCP server over stdio for Claude Desktop, OpenClaw, Cursor and VS Code, and an OpenClaw Skill installed with `clawhub install snaplii-a2m-payment`.
Is the agent-to-merchant-payments repository licensed?
The README's table of contents includes a License section, but there is no LICENSE file among the top-level entries of the repository and no license value recorded for it.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/snaplii-inc-agent-to-merchant-payments)Star history chart for your README
[](https://hysenlabs.com/projects/snaplii-inc-agent-to-merchant-payments)Was this useful?