> For the complete documentation index, see [llms.txt](https://socialcli.gitbook.io/socialcli-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://socialcli.gitbook.io/socialcli-docs/payments-and-credits.md).

# Payments & Credits

## Payments and Credits

### How Credits Work

Every action costs credits. Credits are included with your plan and can be topped up with USDC at any time.

| Action                                          | Credits |
| ----------------------------------------------- | ------- |
| Create a post (per platform)                    | 3       |
| Create a Twitter/X post with URL (per platform) | 20      |
| Retry a failed post                             | 2       |
| Upload media                                    | 1       |
| Get analytics                                   | 3       |
| Get Facebook Page insights                      | 3       |
| List conversations                              | 2       |
| Send a message                                  | 2       |
| Reply to a comment                              | 2       |
| Send a broadcast                                | 5       |
| Most read operations                            | 1       |

### Plans

| Plan     | Monthly | Yearly | Credits/mo | Social Accounts |
| -------- | ------- | ------ | ---------- | --------------- |
| Free     | $0      | $0     | 0          | 0               |
| Standard | $9      | $90    | 200        | 1               |
| Team     | $29     | $290   | 800        | 3               |
| Pro      | $59     | $590   | 2,000      | 7               |
| Ultimate | $99     | $990   | 4,000      | 14              |

Annual billing saves 17% across all paid plans.

**Plan features:**

| Feature              | Free | Standard |   Team   |    Pro   | Ultimate |
| -------------------- | :--: | :------: | :------: | :------: | :------: |
| API and MCP Access   |  No  |    Yes   |    Yes   |    Yes   |    Yes   |
| Scheduling and Queue |  No  |    Yes   |    Yes   |    Yes   |    Yes   |
| Analytics            |  No  |    Yes   |    Yes   |    Yes   |    Yes   |
| Inbox and Comments   |  No  |     -    |    Yes   |    Yes   |    Yes   |
| Webhooks             |  No  |     -    |    No    |    Yes   |    Yes   |
| Support              |  No  |   Email  | Priority | Priority |  Premium |

### Top-Up Credits

Purchase additional credits at any time at `/top-up`:

* Rate: 80 credits per $1 USDC
* Minimum: $1 USDC
* Credits are added instantly after payment confirmation
* Credits never expire
* Only available to paid plan users (Standard and above)

### X402 Protocol

Social CLI uses the X402 payment protocol for all USDC payments - subscriptions and top-ups.

**How it works:**

1. Frontend requests a payment URL from the API
2. API returns the X402 target URL with payment requirements
3. Your wallet signs and submits the USDC transaction
4. Backend verifies the payment on-chain and activates the subscription or credits

**Supported networks:**

* Solana (primary) - USDC on mainnet
* Base - USDC on Base mainnet
* Ethereum - USDC on Ethereum mainnet
* Polygon, Arbitrum, BSC - also supported

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://socialcli.gitbook.io/socialcli-docs/payments-and-credits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.