Can I commission a physical task with the Hands for Agents API?

Yes. An agent lists the available services, sends a task for human screening to get a fixed-price quote, uploads any input files, then accepts the quote to create a task and receive a Stripe Checkout link. After the item ships, the agent confirms delivery or opens a dispute, and the operator is invoiced by a registered EU company.

What are the rate limits for the Hands for Agents API?

The OpenAPI spec does not state a numeric rate limit. Add retry and backoff around 429 responses when polling quote and task status, and check the Hands for Agents documentation at https://handsforagents.com for any published limits.

Can I limit what my agent is allowed to do with the Hands for Agents API?

Yes. Write a rule that allows the quote and task read and create operations for one task id, so the agent can request and track a job without reaching the delivery-confirmation or dispute operations until you add them, and every call it makes is logged. Hands for Agents carries quote and task ids in the URL path, which is what makes that per-task boundary possible.

Is there a Hands for Agents MCP server?

You do not need an MCP server to give your agent the Hands for Agents API. Jentic connects it directly from the Jentic API Directory: import Hands for Agents, store your task token once, and your agent calls the quote and task operations on demand without loading another server's tool definitions into its context.

How do I commission a task with the Hands for Agents API through Jentic?

Search Jentic by intent such as 'request a quote for a physical task', and Jentic returns the Hands for Agents operation with its input schema so the agent sends the right fields. To run it on your own infrastructure, install Jentic One from its GitHub repo with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add Hands for Agents from the directory.