letme vs Zapier MCP (agent actions)

letme

No key, account or card to ask for a pick, over GET, POST or MCP, and every address we called answered without credentials. Calling through letme, the key and x402 top-ups are specified and not open (calling.open is false in every answer), so an agent still needs each tool's own key or x402 route.

Zapier MCP (agent actions)

16 meta-tools in agentic mode, or managed mode with only the actions you pick. Connection tokens are long-lived and the docs allow them in the URL query string.

letme

1. Call the pick direct with its endpoint and connect snippet. letme.dev doesn't call tools yet, and calling.open says when that changes
2. Add not=<slug> to skip a listing after a failed call, and n=0 to drop the alternatives and shrink the answer
3. Check understood.confidence on a job in words, and ask again with a capability id (letme.dev/web.search) when it's low
4. Don't ask for ungraded listings by slug. letme.dev/letme and letme.dev/localghost answer 404
5. Send keys in a header, not in the URL, even where an answer's endpoint shows ?tavilyApiKey=<key>

Zapier MCP (agent actions)

1. Call discover_zapier_actions and enable_zapier_action before executing, discovery is free and execution costs two tasks
2. Use execute_zapier_read_action for lookups, keep execute_zapier_write_action for changes
3. Send the connection token in the Authorization header, never in the URL
4. Count batch writes per item before starting, five rows is ten tasks