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

# Stripe

The Stripe connector gives the Notara agent access to your Stripe account — customer data, subscription status, invoices, revenue metrics, and more. Perfect for growth and ops teams who need revenue answers without logging into the Stripe dashboard.

## What It Enables

| Tool                         | Capability    | Description                                       |
| ---------------------------- | ------------- | ------------------------------------------------- |
| `stripe_get_customer`        | `read`        | Look up a customer by email or ID                 |
| `stripe_list_customers`      | `read`        | Search customers with filters                     |
| `stripe_get_subscription`    | `read`        | Get subscription details and status               |
| `stripe_list_subscriptions`  | `read`        | List subscriptions (active, trialing, canceled)   |
| `stripe_get_invoice`         | `read`        | Retrieve a specific invoice                       |
| `stripe_list_invoices`       | `read`        | List recent invoices for a customer               |
| `stripe_get_mrr`             | `read`        | Calculate current MRR across active subscriptions |
| `stripe_get_charge`          | `read`        | Look up a specific payment/charge                 |
| `stripe_create_invoice_item` | `write`       | Add a line item to an upcoming invoice            |
| `stripe_void_invoice`        | `destructive` | Void an issued invoice                            |

Most common operations are read-only and execute immediately. Write and destructive operations require approval or confirmation.

## Setup

Notara recommends using a **Restricted API Key** rather than your full secret key — it limits what the agent can do to exactly what you need.

### Creating a Restricted Key

1. In your Stripe dashboard, go to **Developers → API Keys**.
2. Click **Create restricted key**.
3. Give it a name like "Notara agent".
4. Set these permissions:

| Resource      | Permission                               |
| ------------- | ---------------------------------------- |
| Customers     | Read                                     |
| Subscriptions | Read                                     |
| Invoices      | Read + Write (if you want invoice tools) |
| Charges       | Read                                     |
| Balance       | Read                                     |

5. Click **Create key** and copy the key (starts with `rk_live_...`).
6. In the Notara dashboard, go to **Tools → Stripe**, paste the key, and click **Verify & Save**.

For read-only access, you can use an even more restricted key with only `Read` permissions on all resources.

## Usage Examples

**Check a customer's subscription:**

```
@Notara What plan is amir@example.com on, and when does it renew?
```

**Get MRR:**

```
@Notara What's our current MRR?
```

**Find a recent payment:**

```
@Notara Did we receive payment from Next Parallel this month?
```

**Look up churn:**

```
@Notara How many subscriptions were canceled last month?
```

## ChartMogul Integration

If you also have the **ChartMogul connector** active, the agent can cross-reference Stripe data with ChartMogul's analytics for richer revenue insights: cohort analysis, LTV, churn rate over time, and expansion MRR. The two connectors complement each other — Stripe for current state, ChartMogul for trends.

## Security Recommendations

* Use a restricted key (not your full secret key) scoped to the minimum permissions Notara needs.
* Avoid granting write permissions unless you specifically want the agent to be able to modify invoices.
* Treat `stripe_void_invoice` as a destructive operation — it's configured as `destructive` capability by default, meaning any user will see an in-channel confirmation prompt before it executes, and only admins can initiate it.

## Live vs Test Mode

Notara works with both live and test mode Stripe keys (`sk_live_...` / `rk_live_...` vs `sk_test_...` / `rk_test_...`). We recommend connecting your live key for production use and testing with a test key first. The key type (live vs test) is displayed on the connector tile so you can see at a glance which environment is connected.


---

# 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://notara.gitbook.io/notara-docs/connectors/stripe.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.