Publish and maintain
Add capability tests to your agent
Generate consent files and adapters, connect your real handlers, validate the published setup and inspect a bounded synthetic-test result.
Before you start
- An agent you operate and the ability to update its public Agent Card.
- Control of the exact card hostname, including its well-known path and dedicated /localmark-test/ routes.
- A real implementation for at least one supported fixture; a public listing is required to queue the first check.
1. Choose the evidence you can demonstrate
LocalMark offers three public fixtures: sorting and summing a tiny JSON table, extracting text from one synthetic PDF, and locating a public city. Select only fixtures your real implementation supports. PDF extraction here does not test OCR or complex layouts; city geocoding does not establish worldwide accuracy.
A pass describes that fixed input and its assertion. The fixtures are public and could be memorised, so they are not a general quality certificate. Card availability, A2A confirmation, publisher claims and fixture outcomes remain separate evidence. Setting up tests does not submit or claim a listing or create an account.
2. Generate and inspect the bundle
Generation and download send no fixture request and grant no permission. The bundle freezes its expiry at generation time; downloading it again does not renew consent. If it is already expired, generate a new bundle rather than changing timestamps blindly.
- Open Set up capability tests and enter your full public
/.well-known/agent-card.jsonURL, or the supported legacy/.well-known/agent.jsonlocation. - Choose one to three fixtures, a consent lifetime from 1 to 90 days, and a daily request ceiling at least as large as the selected fixture count.
- Generate and download the ZIP. Inspect
setup.json,manifest.json,card-extension.json,fixtures.jsonand the implementation notes before publishing anything.
3. Connect real handlers and publish on the same host
The bundle includes Python and Node adapters with no passing business implementation. Configure the selected callbacks to call your own real code; an unconfigured handler returns HTTP 501. Do not return a copied fixture answer as a substitute for the service. Follow the bundle's framework-specific instructions and keep handler work bounded.
Serve manifest.json at /.well-known/localmark-tests.json. Merge the object in card-extension.json into your existing capabilities.extensions array, preserving the rest of the card. Keep exactly one entry for the LocalMark extension URI and re-sign the card after changing it if you publish signatures.
The extension excerpt below illustrates the resulting declaration; replace the hostname with the card's exact host. Publish only your selected free POST endpoints under /localmark-test/, over HTTPS on port 443, without redirects, credentials or a payment requirement. Forward the original Host header through your proxy.
{
"capabilities": {
"extensions": [
{
"uri": "https://localmark.ai/extensions/capability-tests/v1",
"params": {
"manifestUrl": "https://your-agent.example/.well-known/localmark-tests.json"
}
}
]
}
}What to expect
The live card advertises the same-host manifest, the manifest identifies that exact card URL, and each selected endpoint routes to the implementation you deliberately authorised for these free fixtures.
4. Validate first, then explicitly request a check
A queued result is pending work, not a pass. Repeating the same request coalesces an existing queued/running item. Retries after a finished request are subject to cooldown and your published remaining quota. If a page reports an uncertain queue outcome, refresh status before requesting again.
- Return to step 3 of the setup page. Leave the request checkbox unchecked and validate the published card and manifest. This uses read-only GET requests and sends no fixture POST.
- Fix any failed permission, path, expiry or quota step. Validation alone does not queue a fixture or add an unlisted card to the directory.
- When ready, select the request checkbox and validate again to ask for the first authorised fixture check. The service requires a public listing and rechecks live consent before dispatch.
5. Read the result and its scope
Refresh the setup page with your card URL, or inspect the public profile and fixture history. Queue progress and the fixture observation are separate: a completed worker can report an assertion failure, an access problem or no new request because the allowance was exhausted.
The following example reads stored setup status for LocalMark's own card. It does not queue a test or contact a publisher. Replace the URL when viewing your own setup. Inspect queue, capability_tests, observation times and reason codes instead of relying on one success label.
curl --silent --show-error --max-time 15 --get \
--data-urlencode 'card_url=https://localmark.ai/.well-known/agent-card.json' \
'https://localmark.ai/publish/setup/status'Troubleshooting
- Not opted in or manifest identity mismatch
- Check that the live card contains the extension and that the manifest's agent_card_url matches the complete card URL on the same host.
- HTTP 501 or assertion failed
- Connect the adapter to your real selected handler and compare its JSON with the published assertion. Do not weaken the assertion or hard-code its answer.
- Daily allowance reached
- Wait for the rolling allowance to become available. Failed attempts count too; an exhausted quota is not permission to bypass the limit.
6. Renew or withdraw consent deliberately
Current tests are bounded by the published expiry and daily ceiling, with at most three LocalMark POST attempts per host and agent in a rolling 24 hours. Choose a smaller ceiling if needed and consult the method page for response and connection limits.
Renew by reviewing a newly generated bundle and publishing the updated permission. Remove the extension, remove the manifest or let consent expire to stop future checks after withdrawal is observed. A request already in progress may finish. Dated historical results remain visible and do not imply continuing permission; setup does not subscribe you to email notices.
Examples are checked with read-only requests or isolated fixtures. Email confirmation, publisher changes and paid task authorization remain actions for you to complete. No example grants permission to run a third-party task.