Agent context | Solvimon

Agent context tells an AI agent how to use a product, product item, pricing plan or quote template. Each of these resources has an agent_context object with a guidance field. Use the field to record when to select a plan, what an item includes, and which deals it is for. The text is for an AI agent, not for a customer. In Desk, the field name is Guidance. This page shows how agents read the field and how to write it.

Why this matters

An agent can do every Desk operation through the API or the MCP server. But an agent knows only the data that the API returns. A typical billing API returns the name, reference, prices and status of a plan. It does not return the purpose of the plan: why it exists, or which of two similar plans is correct for a deal. It also does not show that an item with the name “Platform fee” includes onboarding but not migration. description is not a good location for this data, because customers can see it and it is frequently empty.

If this data is missing, an agent uses names to make a decision. Agent context gives the agent your instructions.

Without agent context	With agent context
For “Use our most extensive plan”, the agent selects the plan with the longest name or highest price.	The agent picks the plan whose guidance says it is the enterprise tier.
Two near-identical plans look interchangeable.	Guidance says which one to pick, and when.
An agent combines a legacy plan with a new add-on.	Guidance names the combinations that are not permitted.
Only your sales engineers know the rules of your catalog.	The rules are on the resource. Every agent and integration can read them.

When to use it

Use agent context when software, and not a person in Desk, selects the part of your catalog to use.

Agent-led quoting

A sales rep asks an assistant to quote a prospect. The agent reads the guidance on your quote templates and plans, selects the correct ones, and drafts the quote. The rep then approves it.

Self-serve signup through an agent

Your own product’s agent recommends a plan to a user and creates a checkout link. Guidance tells it which plan fits the usage the user described.

RevOps and finance copilots

An internal assistant builds plans, versions prices, or answers questions such as “which customers are on the legacy tier”. It reads the same guidance, so it obeys the limits that your team set.

Headless integrations

Your own backend or workflow reads agent_context from the API like any other field and passes it to the model that makes the decision. You do not need Desk or MCP.

How it works

agent_context is an object that currently has one field, guidance. The field contains a maximum of 2,500 characters of free text. You can use line breaks, so you can write a short list instead of one paragraph. Four resources have the field:

Resource	What belongs in it
Product	What the product is in commercial terms, and which customers it is for.
Product item	What the item includes and does not include. Units and their meaning.
Pricing plan	When to select this plan and not a similar one, and the type of deal it is for.
Quote template	Which situation the template is for, and what the sales rep still has to decide.

You read and write the field in the same way as other fields on those resources. Customers do not see it. It does not appear on an invoice, in the customer portal, or on a quote that the customer sees.

How agents read it

Through the MCP server. Solvimon’s MCP server gives the guidance to the agent together with the catalog metadata. The get_agent_context tool returns only the identity fields of a resource and its guidance. An agent can thus compare plans or templates with a small response before it selects one.
Through the API. agent_context is part of the resource in every response, so your own agent or integration gets it with no extra call.

Guidance is advisory

Guidance helps the agent to make a selection. It does not give permissions. The user’s request always has priority. Guidance cannot authorize a discount, skip an approval, or start an action that the user did not request. If guidance conflicts with the user’s request, the MCP server tells the agent to obey the user and to report the conflict. Approvals and Desk permissions apply as usual.

Implementation

Via API

Set the guidance with a PATCH on the resource, for example PATCH /v1/pricing-plans/{id}:

Add guidance to a pricing plan

curl -X PATCH https://test.api.solvimon.com/v1/pricing-plans/growth-2026 \
  -H "X-API-KEY: <apiKey>" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_context": {
      "guidance": "Mid-market plan, 50 to 500 seats. Pick this over Starter once a prospect asks for SSO or a custom contract, and over Enterprise when they do not need a dedicated environment. The committed API volume is annual, not monthly; overage is billed per 1,000 calls. Do not combine with the legacy Growth 2024 plan on the same subscription."
    }
  }'

Response

{
  "object_type": "PRICING_PLAN",
  "id": "ppla_5RmXe2QbtKfYuA9DcNH3P",
  "reference": "growth-2026",
  "agent_context": {
    "guidance": "Mid-market plan, 50 to 500 seats. Pick this over Starter once a prospect asks for SSO or a custom contract, and over Enterprise when they do not need a dedicated environment. The committed API volume is annual, not monthly; overage is billed per 1,000 calls. Do not combine with the legacy Growth 2024 plan on the same subscription."
  }
}

The same shape applies to products, product items and quote templates. Send "agent_context": null to clear it.

Via MCP

Ask your agent to write the guidance, or call the tools directly. To write guidance through MCP, use the test server (test.mcp.solvimon.com). The live server is read-only by default and has no write_agent_context tool. On live, set guidance via the API, unless Solvimon enabled write access for your account.

write_agent_context replaces the full guidance string. Thus, first read the current text with get_agent_context. Then write the merged version. An empty string clears the guidance.

Set guidance on a pricing plan

{
  "resource_type": "pricing_plans",
  "id": "ppla_5RmXe2QbtKfYuA9DcNH3P",
  "guidance": "Mid-market plan, 50 to 500 seats. Pick this over Starter once a prospect asks for SSO or a custom contract."
}

When an agent creates a product or product item with write_product_catalog, it can include agent_context: {guidance} in the body. The resource then has guidance from the start.

Use this prompt first: “Go through our active pricing plans and quote templates, and draft agent guidance for each one. Show me the drafts before writing anything.” Review the drafts. Then let the agent write them.

Via Desk

Open a product, product item, pricing plan or quote template. Fill in the Guidance field on its detail screen. An empty field shows suggestions. Desk saves the text with the resource, and the API returns it as agent_context.guidance.

What to write

Write the instructions that you give to a new sales engineer. Do not write marketing text.

The decision. “Pick this over Starter once they ask for SSO” helps an agent. “Our flexible mid-market plan” does not.
The limits. Agents frequently make mistakes about what an item does not include.
The exceptions. Plans that you must not combine. Units that are annual and not monthly. Items that look the same but are different.
Current data. The field is free text, so Solvimon does not validate it against the plan. Keep it up to date, because an agent also acts on old guidance.

An agent can act on guidance and can repeat it in an answer. Do not put credentials, customer names or internal cost prices in this field.

Edge cases

It does not change billing. guidance has no effect on pricing, invoicing or entitlements. Only agents use it.
The limit is 2,500 characters. The API rejects a longer value. If you need more text, consider two plans.
Only four resources have it. Subscriptions, customers and invoices do not. agent_context is an object so that Solvimon can add more fields to it later.