Authenticate
Confirm request method, bearer token, access-key reference, and trusted agent or client context.
Wever Labs functions carry intake, dispatch, execution, provider activation, pilot state, receipts, callbacks, and audit events. This rail gives each function a common validation path before it writes to Supabase or advances an operating workflow.
Each runtime endpoint can use the same checks before creating intake records, Work Orders, execution commands, provider events, result contracts, receipts, callbacks, ledgers, or attestations.
Confirm request method, bearer token, access-key reference, and trusted agent or client context.
Check tool scope, run contract, credential envelope, and allowed runtime action before advancing work.
Inspect required fields, schema version, task token, Work Order ID, provider event, callback URL, and payload shape.
Write accepted records through server-side service-role functions and return an explicit response envelope.
Record accepted, rejected, failed, retried, and overridden function activity for console and proof trails.
The validation rail keeps function behavior consistent across TokenOps, FinanceOps, and EnergyOps without burying the OS in one-off endpoint logic.
Requests bind to agent ID, client ID, credential envelope, access-key reference, task token, and allowed tool.
Runtime functions check schema version, required IDs, tool type, provider reference, callback URL, and result envelope shape.
Accepted, rejected, persisted, failed, and pending states return a machine-readable response contract.
Each important auth or validation decision can be written as an audit event tied to task, Work Order, tool, and agent.
Move from validation into runtime function wiring, service-role policy, callback delivery, or TokenOps pilot execution.