SOC 2 Compared

Two providers side by side, as markdown: taglines, pricing, API availability, tags — the researched compare facts, honest about unknowns.

The Published providers in one category, in the order its category page prints (ranked by what we can confirm: a public price, an API and docs, independent sources, stated limits), as a markdown answer sheet. Payment never moves a row.

One provider in full, as answer-first markdown: the summary, then every question on the sheet with its answer, the vendor's own words for it and the URL that proves it. Identical to /{slug}.md and to the HTML page.

SOC 2 Compared's categories with their live listing counts, 0 for one with none yet.

What the SOC 2 Compared owner dashboard shows about the listings an account owns: each one's status (`status.kind`: review with the expected date, accepted with `liveOn` and `paid` ('express' | 'featured' | null: the paid way that releases it, Featured including VIP listing), live, refused with the reason, or archived), the listing as it shows, where AI answers named the product or cited its page, and what it can buy here at this site's prices. Only for the account itself: send its session Cookie header, or its agent key with "Read your listings" as Authorization: Bearer. Same answer as GET https://soc2compared.com/api/owner/listings. Read-only: corrections go through the dashboard's request form.

Full-text search over SOC 2 Compared's Published providers. Returns compact records (name, slug, tagline, url). Fetch depth with get_listing.

Send a buyer-intent enquiry (lead) to a provider or a whole category on SOC 2 Compared. Keyless. Requires consent:true, a real name, a permanent (non-disposable) email, a message of at least 20 chars, and a target (listingSlug OR categorySlug). Returns { ok, delivered }. Idempotent by (email, target) within 7 days. Nothing here changes a listing's rank, tier or copy.

Submit a provider to SOC 2 Compared: the url alone; we write its name and description from its own pages. Requires an existing signed-in account with verified email; send its session Cookie header on the MCP request, or an agent key the account made at https://soc2compared.com/dashboard/agents as Authorization: Bearer. Identity and email come only from that session or key. Sign in or explicitly create an account at https://soc2compared.com/login?next=%2Fsubmit and verify its email before retrying. This tool creates no account and sends no verification email. Returns {httpStatus:201, id, slug, status:'Draft'}; research + the quality gate decide publication. Your own (url, session email) replay within 24h returns httpStatus:200. The fit check starts at once and usually answers within a minute: poll GET https://soc2compared.com/api/submissions/{id} and wait the Retry-After seconds it sends while fit is "checking". fit then reads "accepted" (it goes live, and the account is mailed), "rejected" (mailed with the reason) or "undecided" (a person looks within 2 days). No session: {httpStatus:401, error:'sign_in_required', message, loginUrl}. Unverified session: {httpStatus:403, error:'email_unverified', message, email, remediation}. The owner must prove the site before anything is listed: the account's address, or an address it proved with a code, must be on the submitted website's domain. Otherwise the answer is the pending state {httpStatus:403, error:'domain_unverified', status:'awaiting_owner_proof', listed:false, message, domain, proveWith, ownerUrl, ownerStep, remediation}: nothing is listed or queued. proveWith names who can receive the 6-digit code (any address at the domain; for a GitHub or other shared-host project, its listed addresses or a one-line file). Submitting for someone else? Give the owner ownerUrl (the submit page with the site filled in): they enter the code there and the listing goes in once proven. With a mailbox at the domain yourself: POST /api/domain-proof/start {url, email}, POST /api/domain-proof/verify {proofId, code}, then submit again. Personal mailboxes (gmail, outlook…) never prove a domain. No refusal creates a listing. Validation returns 400; duplicate/claim responses return 409. Read tools remain keyless.