Developing for Solvimon

Use LLMs and AI coding agents to build your Solvimon integration: machine-readable docs, an installable agent skill, plus an MCP server that lets your agent call the Solvimon API directly.

Using the documentation with LLMs

llms.txt

The llms.txt standard helps LLMs index documentation efficiently, similar to how a sitemap helps search engines. We host two files:

• docs.solvimon.com/llms.txt lists every page in these docs with a short description, so an agent can find and fetch the pages it needs.
• docs.solvimon.com/llms-full.txt contains the full documentation in a single file, useful for loading everything into a model’s context at once.

Paste either URL into your AI tool, or reference it from your agent’s instructions file (for example CLAUDE.md or .cursorrules):

1
When working on Solvimon billing code, consult https://docs.solvimon.com/llms.txt
2
to find the relevant documentation pages.

The Solvimon agent skill

Agent Skills are instruction files that coding agents such as Claude Code load on demand. The solvimon skill gives your agent a working knowledge of the platform: the API surface across all four domains, status lifecycles, the meter-to-invoice setup workflow, event ingestion semantics, and common pitfalls like invoice grace periods and asynchronous event deduplication.

Install it with the skills CLI:

$
npx skills add https://docs.solvimon.com

The skill pairs well with the MCP server below: the skill tells your agent how Solvimon works, and the MCP server lets it act on your sandbox.

The Solvimon MCP server

The Model Context Protocol (MCP) is an open standard that lets AI tools call external services. The Solvimon MCP server exposes the Solvimon API as a set of tools, so a coding agent can create meters, pricing plans, and test customers in your sandbox while you build, instead of you hand-writing API calls to set up test data.

The server runs at https://test.mcp.solvimon.com and authenticates with your test API key (Desk → Settings → API keys).

Connect your coding agent

$
claude mcp add solvimon-test --transport http https://test.mcp.solvimon.com --header "X-API-KEY:<your-api-key>"

For Claude Desktop setup, see the Claude integration.

Tool reference

The MCP server exposes 13 tools. Most follow the same input pattern:

Overview

A typical setup flow chains the tools in dependency order:

get_solvimon_account → manage_product_catalog → create_meter_setup (if usage-based)
→ manage_pricing_plans → create_checkout_link or manage_subscriptions (init)

get_solvimon_account

Verifies credentials and returns the billing entities available to the API key. Takes no input. This is a good first call to confirm the server is correctly configured.

manage_billing_entities

Actions: list, get, update, list_tax_registrations, add_tax_registration, remove_tax_registration

1
{"action": "get", "id": "bile_Kq2mVx8RnT4uLpWe9AhZ3"}

manage_product_catalog

Actions: list, get, create, update, delete, activate, archive, deprecate

Resource types: product_categories, products, product_items, features

1
{
2
  "action": "create",
3
  "resource_type": "product_items",
4
  "body": {
5
    "name": "API calls",
6
    "reference": "api-calls",
7
    "product_id": "prod_Xw3nQr7KmY2vBs8TfLc41",
8
    "model_type": "USAGE_BASED",
9
    "meter_value_calculation_id": "mvc_Jh5tRw9PnX3kMq7VbYd28"
10
  }
11
}

create_meter_setup

Creates a meter, a meter value, and a meter value calculation in one call. Returns the mvc_... id to use in usage-based pricing configurations and product items.

1
{
2
  "meter_name": "API requests",
3
  "meter_reference": "api-requests",
4
  "value_name": "count",
5
  "value_reference": "api-requests-count"
6
}

manage_metering

Actions: list, get, delete, ingest, batch_ingest, calculate

Resource types: meters, meter_values, meter_value_calculations, meter_properties, meter_data, events

Creating meters goes through create_meter_setup; this tool covers everything else, including sending test usage events.

1
{
2
  "action": "ingest",
3
  "resource_type": "events",
4
  "body": {
5
    "meter_reference": "api-calls",
6
    "value": 1,
7
    "customer_id": "cust_AbD3DqausjOYiMNDZY11F"
8
  }
9
}

manage_pricing_plans

Actions: list, get, create, update, delete

Resource types: pricing_plans, pricing_plan_versions

1
{"action": "get", "resource_type": "pricing_plan_versions", "id": "ppve_Zt6yUw2QmK9nXr4VcHb37"}

manage_customers

Actions: list, get, create, update, delete, search, activate, archive, forget, entitlements

1
{
2
  "action": "create",
3
  "body": {
4
    "type": "ORGANIZATION",
5
    "reference": "acme-001",
6
    "billing_entity_id": "bile_Kq2mVx8RnT4uLpWe9AhZ3",
7
    "country_code": "NL",
8
    "timezone": "Europe/Amsterdam",
9
    "organization": {"legal_name": "Acme Corp"}
10
  }
11
}

manage_subscriptions

Actions: list, get, create, update, delete, cancel, archive, void, copy, init

Resource types: pricing_plan_subscriptions, pricing_plan_subscription_groups

The init action subscribes an existing customer directly, without a checkout:

1
{
2
  "action": "init",
3
  "resource_type": "pricing_plan_subscriptions",
4
  "body": {
5
    "pricing_plan_version_id": "ppve_Zt6yUw2QmK9nXr4VcHb37",
6
    "customer_id": "cust_AbD3DqausjOYiMNDZY11F",
7
    "billing_period": {"type": "MONTH", "value": 1}
8
  }
9
}

create_checkout_link

Returns a hosted checkout URL. The customer and subscription are created automatically when the end-customer completes checkout.

1
{
2
  "pricing_plan_version_id": "ppve_Zt6yUw2QmK9nXr4VcHb37",
3
  "billing_period": {"type": "MONTH", "value": 1},
4
  "success_url": "https://acme.com/billing/done"
5
}

manage_invoices

Actions: list, get, create, update, preview, pay, refund, credit, archive, send_by_email, authorize, activate, cancel, pause

Resource types: invoices, payments, payment_schedules

1
{
2
  "action": "preview",
3
  "resource_type": "invoices",
4
  "body": {
5
    "customer_id": "cust_AbD3DqausjOYiMNDZY11F",
6
    "billing_currency": "EUR"
7
  }
8
}

manage_wallets_credits

Actions: list, get, create, update, activate, deactivate, archive

Resource types: wallets, wallet_types, credit_types

1
{
2
  "action": "create",
3
  "resource_type": "credit_types",
4
  "body": {"name": "API Credits", "reference": "api-credits"}
5
}

analytics

Read-only queries over dashboard data (revenue, MRR, churn, usage). Use the three actions in sequence:

1. list_datasets returns available datasets and their datasetId
2. list_fields returns exact field names in model.field form
3. query runs the query

The optional customer_id parameter scopes results to one or more customers.

1
{
2
  "action": "query",
3
  "query": {
4
    "datasetId": "dast_Vc7wPx3TnR8mKq5YbJd92",
5
    "measures": ["invoice_v2.invoice_line_base_rep_amount_sum"],
6
    "dimensions": ["invoice_v2.product_names"]
7
  }
8
}

solvimon_api_call

Raw API request. Use when no other tool fits.

1
{"method": "GET", "path": "/v1/products", "query": {"limit": "10"}}

Related