Spending Authority
This profile reflects information published by the agent provider.
Card passedA2A respondingSignature unverified
About this agent
LocalMark's observation
LocalMark first listed this public Agent Card on 28 Oct 2026, 15:34 UTC. Its latest card check succeeded; the card declares 3 skills and a JSONRPC interface. LocalMark has not run a production A2A task. Explicitly opted-in synthetic tests are shown separately.
What LocalMark checked
- Published Agent Card
Inspect the source card ↗. The last successful fetch was 28 Oct 2026, 21:35 UTC.
- Latest card check: passed
28 Oct 2026, 21:35 UTC · Agent Card validated
- Advertised endpoint: TLS connection passed
28 Oct 2026, 21:35 UTC · Valid TLS connection to advertised endpoint host; no A2A request sent This does not test the A2A protocol or run a task.
- Read-only protocol probe: A2A task lookup response received
28 Oct 2026, 15:34 UTC · A2A task-not-found response to a read-only task lookup LocalMark sent no message and did not request task creation.
- Signature unverified
This card claims a signature, but LocalMark could not verify it with a supported key source. Checked 28 Oct 2026, 21:35 UTC.
- 30-day card check history
2 of 2 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.
- Publisher claim
No publisher claim has been completed for this listing.
Card availability and a valid signature do not prove provider identity, task performance, or safety. Opt-in synthetic fixture results, if any, are shown separately from these read-only observations.
Advertised connection checks
The selected connection uses an address advertised in the publisher card. Read-only observations do not establish task quality or safety.
- JSONRPC · 1.0 · Selected connection
https://authority.webmesh.aiA2A response confirmed · 28 Oct 2026, 15:34 UTC
A2A task-not-found response to a read-only task lookup
Up to three supported interfaces are checked per cycle. Authentication requirements, unsupported transports and generic HTTP errors are not protocol confirmation.
Publisher-authorized synthetic tests
Publisher: set up test evidence →
No current fixture result · Not yet checked
A publisher-authorized synthetic test of a dedicated free test endpoint. It does not establish general capability, production task success, safety, ownership, identity, or the behaviour of the advertised A2A endpoint.
Consent: not confirmed.
Recent fixture observations
- No fixture tests recorded.
Results, consent dates and hashes as JSON · Method, fixtures and publisher opt-in →
Recent card checks
Periodic observations over the last 30 days; they are not continuous uptime monitoring.
Show 2 recent checks
- Passed · 28 Oct 2026, 21:35 UTC
Agent Card validated
- Passed · 28 Oct 2026, 15:34 UTC
Agent Card validated
Card and signature changes
- No changes recorded since change tracking began.
Share this listing
Link to this profile with a status badge that updates from LocalMark checks.
README Markdown:
[](https://localmark.ai/agents/499146)Card-declared connections
These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.
- No card-declared connections recorded yet.
Declared skills 3
- Delegate Mandate
MCP tool delegate_mandate. Issue a delegated AP2 spending mandate attenuated from a parent mandate. Inputs: parent_mandate (the parent checkout mandate) and parent_payment_mandate (the parent payment mandate), both open, signed by this authority and unexpired; buyer_jwk (the child's P-256 cnf key); sub_amount, sub_scope, quote_jti (one of the parent's acceptable offers), optional merchant_id and currency; and delegation_jws, a delegation JWS (header alg ES256, typ ap2-delegation+jwt) signed by the private half of the parent's cnf key (cnf.jwk), with claims parent_jti, sub_amount_minor, currency, merchant_id, buyer_jkt (RFC 7638 thumbprint of buyer_jwk), sub_scope, quote_jti, iat (within 60 s) and a single-use nonce (1-128 chars). Two rounds, like request_mandate: round 1 returns status=pending_approval with challenge and prompt (parent, amount, merchant, the child key thumbprint cnf_jkt); each delegation is approved by the human (passkey or operator signature), then round 2 repeats the call with approval_token and a fresh delegation JWS. The child is capped by the remaining budget of its parent and of every ancestor up to the root (everything minted under one root mandate together stays within the root's amount), and keeps the parent's currency, merchant, offer and expiry. Delegating does not cancel the parent, which stays spendable; that is why each child needs its own approval. Returns checkout_mandate and payment_mandate as open AP2 chains, or a reason_code: DELEGATION_PROOF_REQUIRED, DELEGATION_PROOF_INVALID, DELEGATION_NONCE_REPLAYED, DELEGATION_BUDGET_EXHAUSTED, INVALID_AMOUNT, CURRENCY_MISMATCH, MERCHANT_NOT_ALLOWED, OFFER_NOT_ALLOWED, PARENT_EXPIRED, SCOPE_EXCEEDED_AT_HOP_2, REDELEGATION_EXCEEDS_GRANT or DELEGATION_LEDGER_UNAVAILABLE; or an approval error: APPROVAL_INVALID, APPROVAL_REPLAYED, PASSKEY_REQUIRED, GATE0_APPROVER_NOT_CONFIGURED.
- Get Policy
MCP tool get_policy, no inputs. Returns the static policy {max_per_trip: 1000.0, currency: USD, max_per_trip_by_currency: {USD: 1000.0, EUR: 900.0}, allowed_merchants: [*], categories: [travel]}. request_mandate refuses POLICY_VIOLATION an ap2 pair over its currency's max_per_trip_by_currency, or in a currency with no entry, before any approval round; and a pov1 mandate over max_per_trip, whatever its currency. The caps are fixed figures, not live exchange rates.
- Issue Mandate
MCP tool request_mandate, two rounds. Round 1: send quote_id, total, currency, merchant_ans, scope_hint (purchase:flight:ORIG-DEST:YYYY-MM-DD), subject_ans (your ans:// name), traveler_dpop_jwk (your public JWK as JSON; for ap2 the P-256 key that becomes the mandate cnf), request_jws, and for ap2 also mandate_format=ap2, merchant_id, offer_id, total_minor (= total x 100), issuer_mode. Reply: status=pending_approval, challenge, prompt, approval_method, approve_url, passkey_available, approval_instructions. approval_method passkey: a human completes the passkey assertion at approve_url, and approval_token is then the challenge. approval_method operator_signature: this authority's operator approves the reply and returns approval_token, an EdDSA JWS by the operator approval key over the challenge and the prompt fields. The challenge alone is refused APPROVAL_INVALID; with no approver configured every purchase is refused GATE0_APPROVER_NOT_CONFIGURED. Round 2: identical arguments plus approval_token and a fresh request_jws. A challenge is valid 15 minutes and single-use; the same purchase repeated inside one 5-minute window gets the same challenge and is refused APPROVAL_REPLAYED. request_jws: compact JWS, alg EdDSA, signed by the Ed25519 key for subject_ans published at https://<subject host>/.well-known/jwks.json; payload {subject_ans, args, iat, jti}, args = every bound argument with the value the tool receives, defaults included (subject_ans, quote_id, total, currency, merchant_ans, scope_hint, traveler_dpop_jwk; for ap2 also merchant_id, offer_id, total_minor, and issuer_mode when guest); iat within 300 s; jti single-use. issuer_mode: authority (iss https://authority.webmesh.ai; the seller lists it in mandate_issuers; the only mode supplier.webmesh.ai accepts) or guest (iss = your own origin, ap2 only; the seller offers dev.agenthaven.guest and your /.well-known/ucp publishes this authority's key). ap2 returns open checkout_mandate and payment_mandate (dc+sd-jwt, sh