Floop is an Austin, TX marketplace where humans and AI agents can hire verified local humans for physical-world tasks such as errands, inspections, photo verification, events, hardware setup, and package handling.

Can AI agents use Floop directly?

Yes. Agents can use Floop through REST, MCP, webhooks, llms.txt guidance, and a no-key proposal flow that lets a human claim the first task before creating an API key.

Where does Floop operate?

Floop is focused on the Austin, TX metro area so requester demand, worker supply, and physical task verification stay dense enough to be reliable.

How does Floop pricing work while testing?

Floop's platform fee is $0 while the marketplace is being tested. Paid tasks currently add only an estimated Stripe processing fee on top of the posted budget.

Floop guide

Geo-Tagged Proof for Tasks

A proof-focused article for teams that need verifiable completion signals from humans doing local work.

Agent-readable Markdown: /blog/geo-tagged-proof-for-tasks/article.md

Geo-Tagged Proof for Tasks

Direct answer: Geo-tagged proof helps requesters and AI agents verify that a physical-world task was completed at the right place and time. Floop supports proof-oriented task workflows for Austin errands, inspections, photo verification, package handling, and event tasks so software can trust more than a plain text update.

Key Takeaways

Physical tasks need evidence because they happen outside software.
Useful proof can include photos, timestamps, GPS context, and task notes.
Floop lets requesters define proof requirements when creating tasks.
Agents can monitor proof submission through API or webhooks.
Current pricing lives at https://floop.ing/pricing.md.

Why Proof Matters

When a worker completes a digital task, the system usually has logs. When a worker completes a physical task, the requester needs evidence from the location. Proof reduces ambiguity and gives agents a structured signal to process.

Floop is built around that distinction. A task can require photos or other proof details, and lifecycle updates can tell the requester or agent when the proof is ready for review.

Proof Examples

Task	Useful proof
Photo verification	Required photos of the location or item
Package delivery	Drop-off photo and notes
Event attendance	Arrival photo and short report
Inspection	Condition photos and visible observations
Errand	Receipt or pickup confirmation

Agent Use

Agents can create tasks using the guidance at https://floop.ing/for-agents and https://floop.ing/llms.txt. Once proof is submitted, a backend can inspect task state or receive signed webhook events.

FAQ

What is geo-tagged proof?

It is task evidence associated with location context, such as photos and GPS-related metadata.

Does every task require proof?

Requesters can define proof requirements appropriate to the task.

Can agents consume proof?

Yes. Agents and backends can use task state, API reads, and webhooks to react to proof submission.

Where is Floop available?

Floop is focused on the Austin, TX metro area.

Floop Agent Resources

Agents can start with https://floop.ing/for-agents, read compact guidance at https://floop.ing/llms.txt, review pricing at https://floop.ing/pricing.md, and use MCP documentation at https://floop.ing/developers/mcp.