SalesDogg
Start free
For coding agents

Set up SalesDogg from your coding agent

Paste one prompt into Claude Code, Codex, Cursor or any agent that runs commands. It signs in, creates a project, connects your payment provider and proves the setup with the simulator. You approve the sign-in once.

Paste into your agent
Set up SalesDogg (subscriptions and in-app purchases) in this project.

1. Read https://salesdogg.com/llms.txt to learn the product, then https://salesdogg.com/docs/getting-started.md.
2. Run `npx -y @salesdogg/cli login`. It prints a link and a code: show them to me and wait while I approve.
3. Run `npx -y @salesdogg/cli init` to create a project. It writes SALESDOGG_SECRET_KEY and SALESDOGG_PUBLIC_KEY to .env; never print the secret key.
4. Ask me which provider we use (Stripe, Braintree, App Store or Google Play) and connect it with `npx -y @salesdogg/cli apps create`. Read provider keys from .env rather than asking me to paste them. Then import its products.
5. Create an entitlement for the paid features and prove it works with the simulator (`npx -y @salesdogg/cli simulator purchase`) before any real payment.
6. Add the access check and a webhook handler to our code with @salesdogg/sdk.
7. When I'm ready to go live, connect the live keys. The Free plan is sandbox only: if SalesDogg answers with error.type "payment_required", show me error.details.upgrade_url (a link to choose a plan and pay), wait until I say I've paid, then run the same command again.

Every command prints JSON. If one fails, read error.hint and follow it.

What your agent will do.

  1. 1

    Sign in

    You approve

    The CLI starts a device sign-in and prints a link and a short code. You open the link, sign in or create an account, and approve the code. New accounts confirm their e-mail address first. The agent never sees your password.

  2. 2

    Create a project

    Creates the project and its keys and appends SALESDOGG_API_URL, SALESDOGG_SECRET_KEY and SALESDOGG_PUBLIC_KEY to ./.env.

  3. 3

    Turn on payments

    Connects your provider. For Stripe that is a secret key (start with a test-mode key); SalesDogg registers the webhook itself when the API is public. The response lists any manual step, such as pasting a notification URL into App Store Connect.

  4. 4

    Import products and define access

    Pulls the provider's products and attaches the paid ones to an entitlement.

  5. 5

    Prove it with the simulator

    Buys, renews, fails a payment and expires a sandbox subscription, checking access at each step, with no real charge.

  6. 6

    Go live

    You approve

    When you're ready for real payments, the agent connects your live keys. On the Free plan SalesDogg answers with a link to choose a plan and pay, ready to use with no sign-in. The agent shows it to you; once you've paid, it runs the same command again.

  7. 7

    Wire it into your code

    Adds the access check where paid features live, a checkout link or the mobile SDK for buying, and a webhook endpoint that verifies the SalesDogg-Signature header.

Load every operation as MCP tools.

salesdogg mcp serves the whole API as tools over stdio: read operations marked read-only, deletes marked destructive. It needs no key in the config: after login and init it uses the saved sign-in, or SALESDOGG_API_KEY from its environment.

Terminal
claude mcp add salesdogg -- npx -y @salesdogg/cli mcp

Add --scope project to share it with your team through .mcp.json.

Machine-readable, all of it.

/llms.txt
Index of the site for language models, with a link to every page's markdown.
/llms-full.txt
The whole site, docs and API reference included, in one markdown file.
/openapi.json
The OpenAPI 3.1 document the API, CLI and MCP server are all generated from.
/docs/api.md
Every endpoint with its CLI command, MCP tool, credentials and parameters.
salesdogg commands
Prints every CLI command and its parameters as JSON.

Every page of this site has a markdown version at the same address with .md added, for example /docs/getting-started.md.