InfiniteWatch

For personal agents

Connect to the InfiniteWatch company agent

Use this pilot to explain InfiniteWatch's public commercial offering, optionally clarify needs, and prepare contact context. It does not provide customer account access, human support or external submissions.

Poppy 1.0 publication is enabled subject to verified upstream readiness. Retrieve the discovery documents before connecting; an unavailable response means the agent must not be assumed available.

Discover the supported connection profile

Poppy discovery describes the signed-out Poppy 1.0 conversation endpoint and retained company issuer. Poppy 1.0 is the only published Poppy protocol version.

The standard A2A Agent Card describes the HTTP+JSON interface using wire version 1.0, supported public skills and OAuth requirements. A2A version 1.0 is independent of Poppy version 1.0. Compatible clients must implement their chosen protocol and its advertised authentication profile; support varies by client.

Company-agent credentials are limited to public commercial explanation, optional needs qualification and contact preparation. They do not authorize private MCP tools or customer records. No streamed A2A replies, push notifications or extended Agent Card are advertised in this profile.

Self-service credentials for compatible clients

A2A clients can register their public signing keys through the platform's open self-service registration flow, without advance manual key registration or a PAP prerequisite. The platform supports OAuth client credentials with private_key_jwt client authentication and the company-agent:sales scope. Clients retain their private keys locally and use the documented token resource for this A2A interface.

Follow the current platform access profile for registration, key possession, token audience, rotation and revocation. Registration is scoped client access; it does not verify the identity of a person or sign in to an InfiniteWatch account.

Poppy 1.0 signed-out requests carry a Poppy-Session JWT signed with a delegated key and a separate Poppy-Version header declaring the protocol version. No prior session-token issuance or account login is needed; private keys stay with the personal agent. This pilot offers no Poppy account sign-in or browser join.

Identity, retention and your choices

In the company-agent pilot, a client-local asserted identity identifies a conversation within the requesting agent's client. It is not a verified human identity, customer identity or InfiniteWatch account authorization.

Messages, replies, qualification facts, tasks, artifacts and canonical business-event records share a non-sliding 24-hour conversation retention window, measured from conversation creation. Sending another message or renewing a credential does not restart that window. After expiry, clients must not rely on retrieving the conversation or its prepared brief. Save a brief in your own agent only if you want to keep it under that agent's separate storage policy.

Security state has separate expiry: A2A access tokens last at most 15 minutes and can become invalid earlier if the client expires or is revoked. Self-service client registrations expire 30 days after original registration, or earlier if revoked. Rotating keys does not extend that period. Re-registering creates a new client identity without access to the previous client's conversations. Poppy 1.0 uses signed Session headers rather than issued session tokens. The 24-hour conversation retention still applies. Credential renewal does not extend conversation retention. Content expiry does not mean that all security or infrastructure logs or backups are erased at that time.

Sharing needs or implementation context is optional. Do not send passwords, policy, claim or customer records, or unnecessary personal contact data. You can ask for public offering information or the official contact route without providing contact details. A prepared contact brief remains for the requesting agent; the pilot does not send it to email or CRM. You decide whether to use the official contact route and what to share there.

Read the company-agent privacy notice and use the official contact route when you choose to contact InfiniteWatch. Merely preparing a brief does not submit it.

Existing MCP and WebMCP access

The existing MCP connection details and WebMCP guide remain available. Private MCP tools require the existing InfiniteWatch OAuth authorization and account permissions. Company-agent public-sales registration does not replace that separate path.

MCP catalog calls may ignore Poppy Session claims. They do not join conversation state or grant private permissions. The stable WebMCP SDK installation remains the existing connection path.

Company agent access · InfiniteWatch