satsgate
Charge AI agents in Lightning and USDC on the same 402. Payments go straight to your wallet. 500 free unlocks a month.
No node to run, and no custody: the buyer pays the seller's wallet. After 500 free unlocks in a UTC month, each paid unlock debits 2 sats from a prepaid service balance, capped at 10% of the item price.
satsgate init takes a merchant from nothing to a self-hosted paywall config. It opens a free account, saves the account key in .satsgate/account.env, asks for a Lightning Address, mints a restricted proxy key, writes .env and satsgate-proxy.yaml, and checks the paywall with a real 402. That check does not pay, verify, or settle.
Terms: https://satsgate.org/terms. Source: https://github.com/Mike-io-hash/satsgate. API reference: https://github.com/Mike-io-hash/satsgate/blob/main/docs/api.md.
It does not ask for a seed, a private key, or a recovery phrase. It does not hold sats or USDC. The account key is not copied into the project .env. The project .env holds SATSGATE_API_KEY (sgr_) and SATSGATE_ORIGIN_SECRET.
uvx satsgate init
or pip install satsgate, then satsgate init.
Human and agent
Human mode prompts when stdin is a terminal and --json is not set. Agent mode (--json, or stdin that is not a terminal) never prompts. It prints one JSON object on stdout and notes on stderr. A missing Lightning Address is exit 2 and names --lightning-address.
satsgate init --json --lightning-address merchant@pay.example
satsgate init --json --lightning-address merchant@pay.example --want-usdc
satsgate init --docker --framework fastapi
JSON (schema_version 1) includes ok, status, exit_code, api_url, account (client_id, key_preview, fingerprint, reused), payee_lightning_address, usdc, files, route, test_402, start_command, next_steps, warnings, and error. A key is shown as sg_… or sgr_… plus the last four characters, and as a fingerprint. The connect link is not a JSON field.
Exit codes: 0 done, 1 the API or the network failed, 2 usage, 3 a human has to decide, 4 rate-limited. A 429 includes retry_after_seconds and is not retried.
Files
| Path | Mode | Contents |
|---|---|---|
.satsgate/ |
0700 | directory |
.satsgate/account.env |
0600 | SATSGATE_ACCOUNT_KEY |
.satsgate/.gitignore |
* |
|
.env |
0600 when created here | SATSGATE_API_KEY, SATSGATE_ORIGIN_SECRET |
satsgate-proxy.yaml |
proxy config, no secrets | |
.satsgate/connect-link.txt |
0600 | wallet link in agent mode |
A second run reuses the account and the keys. An existing YAML or snippet is not overwritten (agent exit 3 file_exists). A different SATSGATE_* value is exit 3 env_conflict. A symlink is refused. On Windows the run finishes and warns permissions_not_restricted; WSL is the supported way to get owner-only files.
USDC payments: Base network only
USDC payments use Base only. Ethereum mainnet, Polygon, Solana, Arbitrum, and any other chain are not accepted.
| Network | Network id | Circle USDC contract | Status |
|---|---|---|---|
| Base Sepolia (testnet) | eip155:84532 |
0x036CbD53842c5426634e7929541eC2318f3dCF7e |
Testing. It is not a network for real buyers. |
| Base | eip155:8453 |
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
Live mode (on by default on api.satsgate.org; a self-hosted core needs SATSGATE_X402_CDP=1 and CDP credentials, see self-hosting). |
payTo must be an address you control on Base. The USDC moves from the buyer to that address. Satsgate does not hold a buyer wallet and does not run its own facilitator.
--want-usdc mints a one-time connect link when the EVM payee is not verified yet. A terminal prints the link once and can open it. Otherwise it is written to .satsgate/connect-link.txt and is not printed. After the payee is verified, a later run sets x402: true and x402_mode: test. The unpaid 402 then includes a Base Sepolia offer. Paying that offer is a later step for a buyer agent (satsgate-mcp-pay), with the key on the buyer's machine. Test mode is free.
To turn USDC test mode off, delete the YAML and run init again. It is regenerated and the keys are reused. Manual edits to the YAML are lost. To keep them, remove the route's x402 and x402_mode lines and restart the proxy instead.
Lightning has no test network. A paid Lightning request moves real sats to the merchant's own address.
Start
uvx --env-file .env satsgate-proxy --config satsgate-proxy.yaml
satsgate 0.1.2. --docker writes docker-compose.satsgate.yml and prints docker compose -f docker-compose.satsgate.yml up. The compose file uses the public image ghcr.io/mike-io-hash/satsgate-proxy:0.14.2. The generated service listens on 0.0.0.0; the YAML written for uvx stays on 127.0.0.1.
Contributors' note
To build the image yourself, use proxy/Dockerfile from the repo. From a checkout: pip install -e sdk/python -e proxy -e cli.
--framework fastapi, express, or nginx copies the existing origin check. A client that can reach the origin directly must fail closed. The Caddy file in the package is a note, not an HMAC check.
Metadata
Release files for satsgate 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| satsgate-0.1.2.tar.gz | 27.1 kB | With provenance | Details for satsgate-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| satsgate-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for satsgate-0.1.2-py3-none-any.whl |
Total release size: 55.2 kB
Release files / satsgate-0.1.2.tar.gz
| Download URL | satsgate-0.1.2.tar.gz |
|---|---|
| Size | 27.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5fbbd837a5983c1ade0f608e9339ad6e94eeacc6bf940bf6493fede270013a73
|
|
BLAKE2b-256 checksum How to use checksums |
5e08c19e3733b15de9c03300eb4dd8bbe568a2a2c8c9d1f4956f33ea4c6d2467
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / satsgate-0.1.2-py3-none-any.whl
| Download URL | satsgate-0.1.2-py3-none-any.whl |
|---|---|
| Size | 28.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
142922d8138b5387d2e9b92a4a557d93d0f01c05e6c1078d3609bc4b9010a089
|
|
BLAKE2b-256 checksum How to use checksums |
84bff6db176f7f6e30e793bcf15de810d904aeeaf6a2ce391a269029622e0f3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for satsgate 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for satsgate-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.