> For the complete documentation index, see [llms.txt](https://shinkalabs.gitbook.io/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shinkalabs.gitbook.io/hub/andromeda/pricing/catalogue.md).

# Pricing catalogue

You can see what every operation costs before you do anything, with no API key.

## The catalogue

```bash
curl https://api.andromedainfra.pro/v1/pricing
```

This returns the priced operations and their costs. Operations are keyed by stable identifiers (the same keys used internally for analytics), for example `ika.dkg.submit`, `ika.sign.submit`, `ika.recovery.primary.submit`, `encrypt.graph.execute.prepare`, and so on. Use it to plan spend.

It is cacheable at the edge (`Cache-Control: public, max-age=60`), so a short-lived cache on your side is fine.

## Estimate a flow

To estimate a multi-step flow, call the estimate endpoint with the operations involved (this one needs an API key):

```bash
curl -X POST https://api.andromedainfra.pro/v1/pricing/estimate \
  -H "X-Api-Key: $ANDROMEDA_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "operations": ["ika.dkg.submit", "ika.presign.submit", "ika.sign.submit"] }'
```

You get back the total for that set of operations, so you can size, say, "create a wallet, build a presignature, sign once".

## How charging works

* Each call charges your API key's quota by that operation's cost.
* Read-class operations (GETs, challenges, previews, status, ciphertext reads) are cheap; transaction-class operations (signing, prepares, submits, recovery, future-sign, identity) cost more, reflecting the engine work behind them.
* An [idempotency](/hub/andromeda/guides/idempotency.md) replay does not double-charge: a cached response is returned without re-running the operation.
* MCP tool calls charge the same as the equivalent REST call.

See [Quotas & rate limits](/hub/andromeda/pricing/quotas.md) for how quota and rate limiting interact.


---

# 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:

```
GET https://shinkalabs.gitbook.io/hub/andromeda/pricing/catalogue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.