Agent Events · Checks on whether an event’s records agree with each other and with what was announced
Every event record, read against the records behind it.
Event records hold up when the brief carries the purpose, audience, format, dates, capacity and organizer the commissioning note sets; the published agenda runs the plan’s sessions and breaks at the planned times with the planned speakers; every announced speaker has a confirmation for the announced session; the registrations fit the capacity, audiences, conditions and deadline; the venue holds the room, layout, access and hours the brief needs; tickets go on sale at the announced tiers, prices, quantities and refund terms; the announcement claims the dates, venue, price and lineup the brief and schedule hold; and the post-event report states the attendance, sessions and no-shows its records show. Agent Events reads the records an agent or its principal supplies, checks each one for consistency against the document behind it, and returns a signed verdict with the evidence read and what would change it.
- Tool access
- 0.10 USDC / call
- Tools
- Eight tools: eight checks
- Connection
- /mcp
- Result
- Signed report
Start with the two free tools.
On https://weverlabs.com/mcp-free, anonymous and with no wallet, two Agent Events tools map the family and show the brief check at work on synthetic data. Each returns an unsigned result in the family's report shape and ends with a line naming the main tools.
wever_event-snapshot
- Reads
- Nothing, or the situation in hand, such as publishing an agenda, reviewing registrations or reporting on the event, and optionally the names of the documents in hand.
- Returns
- The eight event record checks with what each reads, its four verdicts and when each fits, with the checks that fit the situation listed first.
- Access
- Free on /mcp-free
wever_event-brief-sample
- Reads
- Nothing, or one synthetic event: a product launch, a community meetup or a training workshop.
- Returns
- A synthetic event brief consistent with its commissioning note beside a divergent one, both read by the brief check’s own reading, with the purpose, audience, format, date, capacity and organizer annotated with why they pass or fail.
- Access
- Free on /mcp-free
How agents and people use it.
Your agents
- Call
wever_event-snapshot with the situation in hand to see which checks fit first, before reading any record. - Call the check that answers the question on
https://weverlabs.com/mcp: when an event is briefed, when an agenda is published, when a lineup is announced, when registrations are reviewed, when a venue is arranged, when ticket terms are set, when the event is announced and when a post-event report is written. - Read the verdict, the evidence read and what would change it, each report carrying an Ed25519 receipt anyone can verify, signed.
- Act on the verdict and its findings: ask for a corrected brief, agenda, lineup, list, arrangement, ticketing record, announcement or report, the records behind it, or carry on as checked.
You
- See each brief, agenda and lineup read against the commissioning note, plan or confirmations behind it, with the field, session or speaker on each side.
- Read every registration list, venue arrangement, ticketing record, announcement and post-event report against the terms, brief, schedule or records behind it.
- Verify any check against Wever's published trust key whenever you need to show where a verdict came from.
A worked example
One event brief, read against the commissioning note behind it.
The request
{
"name": "wever_event-brief-check",
"arguments": {
"brief": {
"event": "Lumen Pay Launch 2026",
"purpose": "Launch the Lumen Pay app to merchants",
"audience": "Small business merchants",
"format": "In-person launch event with live demos",
"date": "2026-11-19",
"capacity": 150,
"organizer": "Lumen Pay"
},
"requirements": {
"ref": "REQ-LAUNCH-1",
"event": "Lumen Pay Launch",
"purpose": "Launch the Lumen Pay app to merchants",
"audience": "Small business merchants",
"format": "In-person launch event",
"date": "2026-11-12",
"capacity": 200,
"organizer": "Lumen Pay Inc."
}
}
}What the report returns
Verdict: event_brief_divergent.
| Finding, date differs | The brief sets 2026-11-19 where the requirements state 2026-11-12. |
|---|
| Finding, capacity short | The brief plans a capacity of 150 where the requirements state 200. |
|---|
| Fix, date differs | Set the dates the requirements state in the brief, or record the change in the requirements. |
|---|
| Fix, capacity short | Plan for the capacity the requirements state, or record the lower capacity in the requirements. |
|---|
The event brief diverges from the requirements: date differs and capacity short.
The commissioning note sets the launch for 12 November with room for 200 merchants; the brief moves it to 19 November and plans for 150. The purpose, audience, format and organizer match the note, the format read by its words and the organizer without its legal suffix, so the brief is consistent on four of its six fields. The report states that setting the note’s date and capacity, or recording the changes in the note, moves the verdict to event_brief_consistent.
Call it from your agent.
Connect to https://weverlabs.com/mcp and call any of the eight tools. Each call costs 0.10 USDC on Base. Eligible calls share 10 free calls per wallet over a rolling 30 days with the other paid tools. For free access, send X-Wever-Wallet-Proof signed over the exact JSON arguments and the tool route. The payment challenge supplies the x402 terms for a paid call.
Every report comes with an Ed25519 receipt signed with Wever's published trust key. The Agent Events contract lists the schemas, limits, verdicts and signing details. To run read-only tools on a schedule, Standing jobs; to brief one meeting from its notes or read pricing tiers against plan terms, Diligence checks; to pull every date and obligation from one document, Wever Checks; for an agent’s own commitments against its capacity, Agent Commitments; for trips to an event, Agent Travel and Sports trips; for hiring paperwork, Agent Hiring; and for a service’s reliability records, Agent Reliability.
Browse all tools