Katch coordinates four roles: a creator, an agent, Katch, and human contributors. At a high level, the system converts a question the internet cannot answer into a verified media collection loop.

​
Roles

RoleWhat they do
Creator or funderOwns the mission, funds rewards, receives accepted deliverables.
AgentTurns intent into mission shape, calls the SDK/API, analyzes outputs, and reports to a human.
KatchNormalizes mission input, authorizes fundable terms, verifies submissions, and publishes accepted missions.
Human contributorCaptures the requested photo or video and earns rewards for accepted submissions.
The creator wallet is the source of authority. Draft ownership, webhook subscriptions, and deliverables access all follow the creator wallet, not necessarily the local signer.

​
World and sybil resistance

World is part of the contributor trust layer. Katch uses World ID to establish that a contributor is a verified human, and World App wallets / World Chain provide the native account and reward flow for contributors. Sybil resistance means defending against one actor pretending to be many different people. In Katch, that matters because rewards create a reason to farm missions. A strong mission needs both identity resistance and evidence verification: World ID does not tell Katch whether a photo is good, recent, or relevant. It tells Katch that the submitter passed the human verification requirement. The mission rules, capture requirements, GPS checks, AI verification, and curation decide whether the submitted evidence should be accepted.

​
Mission creation flow

The flow is:
  1. The agent prepares a MissionDraftInput.
  2. Katch previews, normalizes, and authorizes the exact fundable terms.
  3. The creator funds the exact authorized calldata.
  4. The contract creates a funded mission that is locked immediately.
  5. Katch confirms the on-chain mission matches the draft.
  6. Katch publishes the mission to the public feed.
This authorization-first flow prevents agents from hand-encoding unsafe or unclear public missions while avoiding a separate owner-lock step after funding.

​
Capture and verification flow

After publication, human contributors see the mission in Katch, capture the requested media, and submit it for verification. Katch checks the submitted media against the mission rules and may use curation for borderline cases. Only accepted or curation-accepted submissions become creator deliverables.

​
Deliverables flow

Creators fetch deliverables as a manifest: submission IDs, short-lived media URLs, verification results, GPS metadata when available, and provenance. Katch does not run domain-specific extraction in v1. Agents should do their own downstream image/video analysis from the manifest.

​
Notifications

Creators can register webhooks for lifecycle and output events. Every webhook delivery is signed, retryable, and inspectable with katch webhook doctor.