Docs: discover/inspect price.amount is an object in live responses, not a number

Summary

The hosted discover/inspect responses return price.amount as an object with value and currency, while the documentation describes amount as a number and places currency directly under price.

Affected pages:

• https://docs.monid.ai/api/discover.html (response table and example)
• https://docs.monid.ai/api/inspect.html (response table and example)
• https://docs.monid.ai/guide/pricing.html (pricing examples)

Reproduction

Observed on 2026-10-09 (Asia/Taipei), using an authenticated API request. Replace <API_KEY> with your own key:

curl -X POST https://api.monid.ai/v1/discover \
  -H 'Authorization: Bearer <API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{"query":"web search","limit":3}'

curl -X POST https://api.monid.ai/v1/inspect \
  -H 'Authorization: Bearer <API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{"provider":"apify","endpoint":"/apidojo/tweet-scraper"}'

Both returned HTTP 200. The Surf /search/web discover result contained:

{"type":"PER_CALL","amount":{"value":0.006,"currency":"USD"}}

The Apify inspect response contained:

{
  "type": "PER_RESULT",
  "amount": {"value": 0.0004, "currency": "USD"},
  "notes": ["The limit parameter directly controls the maximum number of results returned and charged."]
}

The MCP endpoint https://mcp.monid.ai/v1 also returned the nested amount structure for monid_discover and monid_inspect with provider=surf, endpoint=/search/web, in result.structuredContent and its text-content copy.

In contrast, the docs use a shape such as:

{"type":"PER_CALL","amount":0.003,"currency":"USD"}

The issue is the field structure, independent of individual endpoint rates: integrations following the docs treat an object as a numeric price and read a missing price.currency.

Requested clarification / fix

Please confirm the supported public schema. If the nested object is intended, update the response tables and examples to document price.amount.value (number) and price.amount.currency (string). If this is an unintended API change, please clarify the compatibility/versioning policy for clients built against the documented numeric amount shape.

This report only used discover/inspect; no paid endpoint execution was needed. No credentials are included.