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

# Agent payments — coming soon

Agent payments will let authorized software agents discover a clearly priced Stockmon service, request a machine-readable quote, pay within a fixed budget, and return a verifiable receipt to the person or organization that authorized the agent.

This is an interface for **bounded commerce**, not permission for an agent to control a user’s wallet without limits.

{% hint style="warning" %}
**Agent payments are coming soon.** There is no paid agent tool, autonomous spending account, agent-payment endpoint, or agent-only `$MON` utility today.
{% endhint %}

## How agent payments work

1. **Discover** — the agent reads a versioned catalog describing one service, price unit, supported network, and required inputs.
2. **Quote** — Stockmon returns the exact amount, asset, recipient, expiry, service commitment, and idempotency key.
3. **Authorize** — the agent checks the quote against the asset, budget, recipient, and time limits set by its owner.
4. **Settle** — one payment is submitted without silently changing the asset, amount, chain, or recipient.
5. **Receipt** — Stockmon returns a stable payment and service receipt that can be independently reconciled.

The agent can stop safely at every boundary before settlement.

## The owner’s spending rules

Every payment binds:

| Field                      | Why it matters                                          |
| -------------------------- | ------------------------------------------------------- |
| Service ID and version     | Prevents a quote from paying for a different operation  |
| Chain ID                   | Prevents cross-network confusion                        |
| Exact token contract       | Prevents a copied ticker from selecting the wrong token |
| Maximum amount             | Caps agent spending in integer token atoms              |
| Recipient                  | Prevents redirection                                    |
| Expiry                     | Stops old quotes from remaining spendable               |
| Nonce or idempotency key   | Prevents duplicate payment after retries                |
| Expected output commitment | Connects payment to the purchased result                |
| Owner rule-set ID          | Shows which budget and rules authorized the agent       |

Budgets and amounts use integer atoms or decimal-safe arithmetic—never binary floating-point money math.

## Where `$MON` fits

Agent payments can use `$MON` for clearly priced Stockmon-native services. Every quote identifies the exact contract, decimals, amount, recipient, expiry, and purchased result.

The canonical `$MON` contract is documented on the [$MON page](/stockmon/mon.md). Every agent quote uses that exact Robinhood Chain address.

## Human control stays above the agent

Agent payments preserve:

* a human- or organization-defined budget;
* owner-approved lists of services, assets, chains, and recipients;
* per-payment and rolling-period caps;
* a visible revoke or pause control;
* no Stockmon-held user private keys;
* no hidden top-up, custody balance, or subscription renewal;
* no silent fallback from a failed live payment to simulation; and
* receipts that distinguish quoted, submitted, finalized, failed, and refunded states.

One successful payment never gives Stockmon or the agent broader spending permission.

## Failure and retry rules

Network failure creates ambiguity. The agent reconciles the quote, sender nonce, transaction hash, recipient, and service receipt before retrying. “The HTTP request timed out” does not prove that a blockchain payment failed.

The payment commitment and service idempotency key prevent duplicates. If the system cannot prove whether a payment or service completed, it stops instead of charging again.

## Still being built

The service catalog, transport protocol, wallet standard, settlement assets, refund model, and launch date are still being built. Until launch, Stockmon does not accept agent payments.

Next: [Status, safety, and risks](/stockmon/status-and-risks.md).


---

# 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://raretyperesearch.gitbook.io/stockmon/agent-payments-coming-soon.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.