ctrify.com valid

CTRify

CTRify is a hosted AI SEO action platform. Customers can use it from Cursor, ChatGPT and compatible AI agents through MCP, or from their own software through an OAuth REST API.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T06:33:29.999Z. Cached copy · Source on ctrify.com

# CTRify

> CTRify is a hosted AI SEO action platform. Customers can use it from Cursor, ChatGPT and compatible AI agents through MCP, or from their own software through an OAuth REST API.

## Developer interfaces

- [CTRify MCP and REST documentation](https://www.ctrify.com/developers): Human-readable canonical setup, authentication, billing, permissions, security, errors and examples.
- [CTRify developer documentation in Markdown](https://www.ctrify.com/developers.md): Low-noise machine-readable version of the complete developer guide.
- [CTRify OpenAPI 3.0 contract](https://www.ctrify.com/api/ctrify/v1/openapi.json): Live REST route and schema contract.
- [OAuth protected-resource metadata](https://www.ctrify.com/.well-known/oauth-protected-resource/mcp): MCP resource, authorization server, supported scopes and CTRify permission profiles.
- [OAuth authorization-server metadata](https://www.ctrify.com/.well-known/oauth-authorization-server): Authorization, token, registration and revocation discovery.

## Canonical endpoints

- MCP: `https://www.ctrify.com/mcp`
- REST base: `https://www.ctrify.com/api/ctrify/v1`

Configure the MCP URL in a Streamable HTTP MCP client. Do not open it as a webpage: `GET /mcp` intentionally returns HTTP 405 because the protocol uses JSON-RPC over `POST` and standalone SSE is not enabled.

The REST base is a namespace, not a resource. `GET /api/ctrify/v1` intentionally returns HTTP 404. Append a documented path or read `/api/ctrify/v1/openapi.json`.

## Required agent behavior

1. For each new goal, call `ctrify_capabilities_search` with the actual desired outcome in `intent` (10–500 characters), concise function keywords in `query`, and retain the returned `intent_ref`. Keep `intent` unchanged when reformulating the query.
2. Use `ctrify_capability_get` for one exact `operation_id`, passing the same `intent_ref`.
3. Inspect the contract, permissions, cost behavior, side effects and execution mode.
4. Use `ctrify_action_execute` only with contract-valid arguments and the same `intent_ref`.
5. Supply a unique stable `idempotency_key` for every mutation.
6. Never send or infer `customer_id`; CTRify derives the customer from OAuth.
7. Preserve native immediate or asynchronous behavior and never infer that a queued action has finished.
8. If the intent is blocked, fails, is partial, confusing or produces an incorrect result, call `ctrify_feedback_submit` with the original intent and completion state.

CTRify retains the bounded intent supplied to catalog search, the operations offered and the linked execution outcome so product gaps can be identified. Obvious accidentally supplied credentials are redacted; normal product intent is retained.

Continue passing explicit intent references. Omitted references can be inferred for audit only from recent unambiguous same-customer/token/client searches that offered the selected operation; ambiguous associations are not guessed. Cached get/execute calls accept a separate optional
…

Related sites

Other listed sites in Marketing. See the whole category →

Machine-readable: GET /v1/resolve?q=ctrify.com · GET /v1/domain/ctrify.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ctrify.com:
1. POST https://agentwebmap.com/v1/sites/ctrify.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://ctrify.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/ctrify.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ctrify.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.