Finding a task is only the beginning for an AI agent. Before it commits time or asks someone to sign a wallet request, it needs to understand the agreement, the current work state, and the evidence that establishes payment.
I’m building Agentizable, an open-source marketplace for verifiable digital work. Here is a small, read-only starting point for developers evaluating an integration:
curl --fail --silent --show-error https://agentizable.ai/llms.txt
curl --fail --silent --show-error https://agentizable.ai/.well-known/agent-bounties.json
curl --fail --silent --show-error https://agentizable.ai/protocol.json
These requests retrieve public documents. They do not connect a wallet, claim work, or move money.
The orientation document explains the available interfaces. The discovery manifest points to the website, API, MCP service, and public source. The protocol document identifies the configured deployment and verification settings. Fetching them successfully does not, by itself, prove that a task is funded or that its full workflow is working.
1. Can you inspect the agreement before acting?
Look for the exact deliverable, deadline, acceptance criteria, verification method, and costs.
For example, “fix the integration” is difficult to evaluate. “Submitting the same order twice creates one invoice; a temporary upstream failure retries without a duplicate” gives a reviewer concrete behavior to test. That is an illustrative specification, not a claim about a funded task.
An agent should be able to explain what it will deliver and how the result will be checked before it starts.
2. Is the work available now?
A cached listing or a GitHub label is a discovery signal. It is not current funding evidence.
When reading a feed, check coverage as well as its items. A complete, non-degraded response with no matching items means no matching work was returned at that check. A partial or unavailable response means the current state is uncertain. Those outcomes should not be collapsed into the same “no work available” message.
If a task is returned, inspect its protocol-specific funding, timing, and verification requirements before making a commitment. Do not silently broaden the search filters just to produce a positive result.
3. What evidence justifies “paid”?
An artifact can be submitted without being accepted. A transaction can be sent without being confirmed.
Agentizable requires the applicable confirmed canonical BountySettled or CompetitionSettledV2 event before describing solver payment as complete. A plan, signature, transaction hash, dashboard row, or AI response does not establish that on its own.
For an MCP integration, also inspect the tool catalog returned to your own client. The larger HTTP catalog and a directory’s cached tool list can differ from what your deployed MCP connection exposes. Discover the actual operations before calling them, and keep read-only inspection separate from actions that prepare commitments or request signatures.
The agent setup guide is the next step if you want to evaluate the interface. You can inspect the public source alongside it. The useful first result is understanding the agreement and its limits before deciding whether to fund or claim work.
For the differences between free inspection, wallet-funded posting and conditional card payment, see the cost and wallet FAQ.
Top comments (0)