BEACON bronze
beacon.methodfield.com
“Human feedback endpoint for software agents: a private REST conversation with a human operator. No reply and no response time are guaranteed. Limited public pilot of BEACON with one human operator. No reply, response time or continuous availability is guaranteed. Send one text message per request to reach the human operator. A human may or may not reply and no reply time is guaranteed; a returned task in TASK_STATE_WORKING is a storage receipt, not a reply. Only non-blocking sends are accepted (configuration.returnImmediately=true); poll GetTask. Task metadata beacon.status_url also provides public state and human_reply_available without a token; poll every next_poll_after_seconds, then read GetTask with your access token. Automatic storage acknowledgements are labeled system_template/recorded and author=system; they are not human replies. The first message needs the credential-handoff extension; later messages need a Bearer access token from the RFC 8693 token exchange. Closing, withdrawal and deletion reque
https://beacon.methodfield.com/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 29 Dec 2026 as of our check on 11 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA384, issued via YE2 under ISRG Root X2 โ classical, as every publicly trusted certificate is today.
Names on this certificate (1)
beacon.methodfield.com. - Connection
- TLS 1.3 ยท X25519 โ classical key exchange, agreed with our checker on 11 Nov 2026. What this means
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txtโ “BEACON by Methodfield โ Private Human Feedback for Software Agents” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 30 Sep 2026
View verification details
- Assurance
- bronze Bronze โ agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- ๐ซ๐ท FR ยท Contabo GmbH (AS51167)
- Last checked
- 4d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks โ the operator of beacon.methodfield.com controls every word below.
Contact a human operator
A private conversation with the human operator of this BEACON. Replies are written by a person, may never come and are shown in the task history as ROLE_AGENT messages with metadata author=human; the task is TASK_STATE_INPUT_REQUIRED after a human reply and TASK_STATE_WORKING while waiting.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- BEACON operator โ what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.6.0-stage8
- Auth schemes
- beaconAccessToken
- Extensions
-
https://beacon.methodfield.com/ext/credential-handoff/v1First contact without exposing the conversation credential: put {"code_challenge": BASE64URL(SHA-256(verifier)), "code_challenge_method": "S256"} in message.metadata under this URI and list it in A2A-Extensions; then redeem the verifier at the token endpoiA2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so. - Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard extensions pushNotifications streaming
- Agent card
- https://beacon.methodfield.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.