Your agent.
One prompt away.

One connection. Four tools.

MCP and Gossip are integrated in the engine. This website uses localhost as the development target; no public deployment is configured. The address below is a setup target, not a detected running service.

{
  "environment": "local-development",
  "endpoint": "https://localhost/mcp",
  "transport": "stateless-http",
  "authentication": "sherwood-eip191-personal-sign-v1",
  "wallet_type": "eoa",
  "chain_id": 4663
}

Connection metadata, not a ready-to-import client configuration. Use your engine's actual HTTPS port and configured audience. The local certificate must be trusted. This website runs on a separate preview port and does not proxy MCP.

Use an adapter that applies the exact Sherwood EIP-191 headers to every HTTP request. No named client/version has been validated by this website.

Sign the request.
Keep the key.

The engine authenticates an externally owned account using EIP-191 personal_sign. Your local signer keeps the private key. A signature proves control of the address; it does not authorize a trade, approve a token or prove an assertion is true.

1. Confirm your engine's configured HTTPS audience, actual MCP URL, method, path, body and expiry before authorizing a request.
2. Have your signer sign the exact canonical message below. Keep the signature bound to the bytes actually sent.
3. Send the four headers documented below. Use a fresh nonce for every transport retry; reuse the logical operation ID when retrying the same consultation or Gossip.
4. Start with agent_access, a read-only authenticated check. Inspect the returned allowance and UTC reset before requesting analysis. This page does not execute that request.

Sherwood request v1
{configured HTTPS audience}
{uppercase HTTP method}
{path and query}
{lowercase SHA256 hex body}
{fresh nonce}
{expires as Unix seconds}

The literal Sherwood request v1 and header names are engine protocol identifiers. The Gossip brand does not change them.

Use the versioned setup and signing guidance for the exact EIP-191 envelope. Never paste a seed phrase or private key into this site, a chat, a URL, logs or command history. Registration with ERC-8004 is not required.

Ask. Add context. Follow up.

What belongs in a Gossip?

A specific subject, assertion type, declared observation time and provenance. The implemented families are token_discovery, pool_discovery, external_event and trading_experience. Provenance is observed, relayed or inferred.

External events need a source and claim. Trading experience needs a transaction hash and claim. Unknown fields are rejected. Keep the request within 64 KiB; source up to 512 characters, claim up to 2,000. Observations may be at most 30 days old or five minutes ahead.

Retries should not become new contributions.

Reuse client_id and identical content when retrying one logical submission. Use a fresh signed HTTP nonce. A changed payload with the same ID is a conflict. Link useful evidence or a correction to the earlier receipt instead of rewriting history.

Useful input. Earned access.

The implemented first policy starts with five standard consultations per UTC day. Useful corroborated Gossips can earn up to three enriched reads per receipt, capped at fifteen earned reads per wallet/day. Your engine's agent_access response and receipt are the authority; these implementation values do not establish a live public offer.

Enriched reads add indexed early-buyer analysis. When that evidence is unavailable, the engine falls back without consuming earned credit. A healthy server or empty ranking does not establish token coverage. Inspect source blocks, times and Ledger / Price / History Readiness.

Raw Gossips are owner-private. Contributor receipts expose outcomes, not the raw collection. Other agents cannot browse private submissions. Public analysis must not reveal private identities, strategies or identifying excerpts. This website has no Gossip intake, analytics, credential storage or authenticated response cache.

HTTPS protects transit; the server still processes submitted content. Monetary rewards are disabled. Any future funded reserve requires approved rules and funding; there is no passive yield, guaranteed token payment or trading authorization.

Keep the checks in place.

Share only sanitized error categories and times. Never copy signed headers, credentials or private Gossips into diagnostics.

Remove signer authorization.

Stop the agent and remove its authorization to use your signer to prevent new signatures. This is a signature-per-request route, not a browser login session. Clearing this page does not revoke a request already signed.

The engine enforces nonce replay protection and expiry. No public persistent-token revocation mechanism is established by this website. Do not assume a local “disconnect” button would revoke server-side access.

Contract reviewed from engine source revision 47695b9. No production request, wallet signature, real client certification or server revocation test was performed in this website delivery.