Configure and test
Agent Card and Pricing
Completion criteria
The Agent Card, MOM, pricing, LLM, and compute resources must all pass page validation before the version is publishable. A successfully saved draft is not the same as a publication-ready version.
Complete the Agent Card
| Field | Required for publication | Constraint |
|---|---|---|
| Avatar | Yes | The published value must resolve to HTTPS. Upload PNG, JPEG, or WebP up to 5 MiB; a 1:1 image is recommended. |
| Name | Yes | State the Agent's capability clearly. |
| Description | Yes | Explain the use case, input, and output. |
| Category | Yes | Exactly one category can currently be selected. |
| MOM | Yes | UTF-8 .md, no larger than 1 MiB, with the complete required section structure. |
Upload an avatar
Select a PNG, JPEG, or WebP file no larger than 5 MiB. Use a square 1:1 composition so the subject is not cropped in catalog and detail views.Enter a name and description
The name should immediately communicate what the Agent does. The description should state at least the intended use case, core input, and expected output. Both fields are required for successful publication.Select one category
The current workspace accepts one category. Choose the category closest to the primary use case instead of trying to represent it with several similar labels.Upload the MOM
Upload a UTF-8 encoded.mdfile no larger than 1 MiB, and verify the minimum structure below.
Published avatar URL requirement
After upload, the avatar in publication data must resolve to an HTTPS URL. A local path, file: URL, HTTP URL, or expired temporary URL cannot be used as the published avatar.
Minimum MOM template
The MOM uses the mom.v1 structure and must contain three complete sections titled exactly Use when, Inputs, and Outputs. Do not alter their capitalization or spacing.
# Summary Agent
## Use when
- The user needs a faithful, concise summary of a passage.
## Inputs
- `text`: the UTF-8 passage to summarize.
- `language`: optional; the requested output language.
## Outputs
- A concise summary.
- A clear request for the missing input when no passage is provided.
The MOM is not marketing copy
It must let a caller decide when to use the Agent, what to provide, and what will be returned. Before upload, confirm that the file is UTF-8, has a .md extension, is no larger than 1 MiB, and does not leave any of the three required sections empty.
Configure pricing
The current pricing model is fixed to cost_plus. Enter the gross margin and Minimum Starting Balance in Credits. The page validates and saves the pricing draft. Publication mapping requires an integer gross-margin percentage; do not rely on a decimal being rounded after save.
| Field | Current rule | Guidance |
|---|---|---|
| Pricing model | Fixed to cost_plus | Do not assume that another model can be selected in documentation or Program logic. |
| Gross margin | An integer percentage from 0 to 100 | For example, 20. A decimal may save but fail at Publish with PRICING_MAPPING_INVALID. |
| Minimum Starting Balance | At least 0, in Credits | Maps to minimum_starting_balance_credits. Set it to the minimum balance needed to complete one representative invocation safely. |
Do not omit required runtime configuration
- At least one LLM capability is configured; an LLM is required for publication.
- Both CPU and memory are selected; both are required for publication.
- Image, video, audio, PDF, or image-understanding capabilities are added only when the Program actually needs them.
- Selected model capabilities match the input types promised by the MOM.
- After saving the draft, refresh the page and confirm that the Agent Card, MOM, pricing, models, CPU, and memory were all retained.
Publication preflight passed
The avatar, name, description, single category, MOM, pricing, LLM, CPU, and memory are valid, and both successful and failure behavior have been tested in WebChat.