Middesk vs Vouched

Middesk

A public OpenAPI 3.1 contract for 87 operations, llms.txt, Markdown docs and a dated weekly changelog make the REST API readable to an agent, and OAuth has a read-only scope. Access is sales-led. No price, self-serve signup or official SDK was found, and the hosted MCP server rejects sandbox keys.

Vouched

Vouched publishes per-transaction prices from $0.75 with a $300 monthly minimum and a 14-day trial, and its docs carry llms.txt, OpenAPI fragments and filterable job search. Rate limits have no number, there is no idempotency key, server SDK or security.txt, and the API status page shows a 70-minute rise in rejections on 1 October 2026.

Middesk

1. Match the key to the host. mk_test keys work only at https://api-sandbox.middesk.com/v1 and mk_live keys only at https://api.middesk.com/v1
2. Name the orders on POST /v1/businesses. Omitting them places a verification order plus every package the account runs automatically, all billed
3. Send address_line1 and address_line2. The API ignores address_line_1 without an error
4. A 201 means the business was created, not verified. Wait for the business.updated webhook or poll until status leaves pending
5. Stay under 20 requests a second per account, and in sandbox wait the seconds in Retry-After after a 429 on business creation

Vouched

1. Use the private key in X-API-Key against verify.vouched.id or verify.eu.vouched.id, matching the account's region
2. Check Find Jobs before resubmitting. There is no idempotency key and each job is billed
3. Pass withPhotos=false and select fields on Find Jobs to keep responses small
4. In a test account, use the name test pass for a clean result and any other name for a failure
5. Back off on 429. All endpoints share one limit and no figure is published