Lolly
ऐप खोलें
सेटिंग्सGitHub
ऐप खोलें

प्रबंधित करेंPartners

Partners' agents

नोट: Lolly Work

This guide covers the optional organisation service. Configuration, console and API paths refer to your Lolly Work instance. The packaged console keeps its release-matched copy of this guide.

A partner can work through an AI agent too. A token you issue for the agent sees what that company's people see: the same tools, files, templates, input rules, company details and licence gate. It reads your brand guidance and its company's details over your organisation's MCP endpoint, and the files it makes record the company and programme, never the agent.

The Agent tokens card for Northwind IT: Rita's agent with its limits, where each figure comes from, today's use and the expiry, then the form that mints a token with a label, a lifetime, what it may do and its limits signed by Lolly Demovector SVG10 paths130 nodes113 groups2 images187 KBCheck it yourselfसाइन की हुई फ़ाइल पाएँThe Agent tokens card for Northwind IT: Rita's agent with its limits, where each figure comes from, today's use and the expiry, then the form that mints a token with a label, a lifetime, what it may do and its limits signed by Lolly Demovector SVG10 paths130 nodes113 groups2 images187 KBCheck it yourselfसाइन की हुई फ़ाइल पाएँ

This page is part of Run a partner programme.

Give an agent a token

On the programme's page, or a company's, the Agent tokens card mints a token for the agent, for the programme or one company, and shows its secret once. Mint token takes a label, the company, the scopes, the days until the token expires and any limits, then shows the secret once, with Copy. Anyone with programme.manage for a programme issues its tokens; a grant of programme.manage on programme:<id> lets its holder manage that programme's tokens only. The server sets what the request cannot: the automation role, the programme's and company's groups and the partner group.

Limits and usage

Every token placed in a programme meets three limits:

LimitDefault
Calls a minute120
Renders a day, in UTC2,000
Renders a month, in UTCNo cap

The Agent tokens card shows each limit with where the figure comes from and today's use against it, with what a limit turned away this week and when. Change limits sets a token's own figures; a blank field takes the programme's. Change the programme's limits sets the figures every token there starts with. The token's own figure wins, then its programme's, then the instance default. A token over a limit is refused with plain words and the time to try again, such as "This token has used its 2,000 renders for today. The budget renews at 00:00 UTC." A render the budget cannot hold is refused whole.

The Agent tokens card on the Limits and quotas tab

The Agent tokens card on the Limits and quotas tab: the default calls a minute and renders a day, their maxima and the token lifetime bounds, each with its source signed by Lolly Demovector SVG141 groups178 KBCheck it yourselfसाइन की हुई फ़ाइल पाएँThe Agent tokens card on the Limits and quotas tab: the default calls a minute and renders a day, their maxima and the token lifetime bounds, each with its source signed by Lolly Demovector SVG141 groups179 KBCheck it yourselfसाइन की हुई फ़ाइल पाएँ

What agents did, on the same page, totals what each token did over the last 4 weeks or the last 7 days, and Download CSV gives the same counts week by week or day by day: calls, renders, batches, deliveries, approval requests and refusals, with totals per company and for the programme. The counts hold no input values, prompts, titles, file names or agent names.

What agents did over the last 4 weeks: calls, renders, batches, deliveries, approvals and refusals for Rita's agent, for Northwind IT and for Resellers, EMEA, then renders by tool signed by Lolly Demovector SVG2 paths26 nodes76 groups175 KBCheck it yourselfसाइन की हुई फ़ाइल पाएँWhat agents did over the last 4 weeks: calls, renders, batches, deliveries, approvals and refusals for Rita's agent, for Northwind IT and for Resellers, EMEA, then renders by tool signed by Lolly Demovector SVG2 paths26 nodes76 groups175 KBCheck it yourselfसाइन की हुई फ़ाइल पाएँ

What an agent reads

The organisation MCP endpoint offers resources to a service token, each read counted as one call:

The same answers are at GET /api/v1/context/* for REST callers.

Templates by purpose

An agent can ask for a piece by what the piece is for, with resolve_intent, rather than by tool. When the agent asks, your templates are offered where their purposes fit. Set a template's purposes with Purposes on the programme's Templates card, which then reads, for example, "This template is for: Promote · Banner, Social landscape". Inputs the company fills count as given, so an agent for Northwind IT is never asked for the partner's mark or the company name. A retired template is never offered.

Worked example: Northwind IT

The worked example on Run a partner programme follows Northwind IT, a reseller in Resellers, EMEA, through every subject. Its seventh step happens here.

7. Give Rita's agent a token

Console. On Northwind IT's page, use the Agent tokens card. Give the label "Rita's agent", keep the default scopes and the 90 days until the token expires, and press Mint token. Copy the secret, which is shown this one time, press I have copied it and hand the secret to Rita.

lw.

lw tokens add --programme resellers-emea --company northwind-it --label "Rita's agent"
Step 7 with the API
POST /api/v1/programmes/resellers-emea/tokens
{ "label": "Rita's agent", "company": "northwind-it" }

The answer is 201 with the token's id (tok_…), label, company, scopes (render and catalog.read by default), expiresAt (90 days on), its limits and today's use, and token, the secret (lwt_…). The secret appears in this answer only.

Rita's agent connects to your organisation's MCP endpoint with the secret. It sees what Rita sees, renders the data sheet with only the price, colourway and mode open, and its files record Northwind IT, never the agent.

Next: 8. End the partnership on a date.

Every option