ComplyAdvantage vs Shufti

ComplyAdvantage

The Mesh API has a public OpenAPI 3.0.3 spec with 165 described operations, per-credential permissions and audit log endpoints, which suits an agent screening customers and working alerts. No status page, changelog, SDK, service agreement or subprocessor list was found in public, and access starts with a paid plan bought by a person.

Shufti

One endpoint covers document, face, address, AML and KYB checks, with a free plan of 10 verifications a month, and a hosted MCP server adds OAuth with three scopes. No OpenAPI file, server SDK or idempotency key was found, and the status page history could not be read.

ComplyAdvantage

1. Exchange the access key and secret at POST /v3/token for a bearer token. It lasts 24 hours and can't be refreshed, so request a new one before expiry
2. Ask for a credential with only the permissions the task needs. Permissions can't be edited later, and each reference page names the ones a call requires
3. Create a screening configuration first and keep its configuration_identifier. Creating and screening a customer needs it
4. Give each customer a unique external identifier. A concurrent request for the same identifier returns 409 with a pointer to the first workflow
5. Read Ratelimit-Remaining and Ratelimit-Reset on every response. A 429 body is only API rate limit exceeded

Shufti

1. POST every verification to https://api.shuftipro.com/ with a unique reference of 6 to 250 characters and one object per service. Read results from /status with that reference
2. Register the callback domain in the back office first. An unregistered callback_url is rejected
3. Stay under 60 requests a minute per IP on a production account and 20 on a trial account
4. Check the Signature response header. Accounts created after 15 March 2023 hash the Secret Key with SHA-256 before appending it to the raw response
5. Through MCP, identity checks return a verification_url for the person to open. No tool accepts an image, so use the REST API for offsite proofs