These four playbooks mirror how teams adopt Inquir first: AI agent backends, webhook processors, cron jobs, and REST API endpoints—each pairs serverless functions with the HTTP gateway, secrets for providers, and observability when something misbehaves. Follow the links to the public use-case hubs for verification, retries, and templates.
AI agent backends
Long-running model calls, tool loops, and structured outputs behind a stable HTTP route. Use streaming when you need partial tokens, and keep provider keys in environment secrets.
Webhook processors
Verify signatures on raw body, return quickly with 2xx, and offload heavy work to async jobs or pipelines when the provider times out.
Cron jobs
Scheduled functions for syncs, reports, and cleanup. Same runtime and secrets as online handlers; use idempotent writes and observability to audit each run.
REST API endpoints
Route groups and authenticated JSON APIs on the gateway. Parse event.body as a string from HTTP invokes; share types between handlers where it helps.