Build your workflow with
the Tityra API
Read Tityra's API and MCP examples and connect tools to the projects you choose. Find permissions, request and report guidance, and the checks required before making changes.
Used by many

READ THE PUBLIC API
Find endpoints and request examples.
CONNECT A CUSTOMER ACCOUNT
Use approved projects and permissions.
BUILD WITH AGENT GUIDANCE
Check supported tools and boundaries.
Copy linkTityra API and MCP quick start
The public endpoints don't require an account or an API key. Start with the permissions endpoint below, then initialise the public MCP connection and list its tools. These examples use the live anonymous service at tityra.com. Customer projects and reports require a separate account connection.
The package example calls get_audit_options with the free plan. It reads the current public Initial Audit package without submitting a request or fetching a target website.
These examples read public information. They don't provide sample customer credentials, private reports or payment authority, and they don't start a scan. Package information comes from the live service. The API reports when pricing is unavailable.
Read public permissionsTerminal
$curl --fail --silent --show-error 'https://tityra.com/api/v1/permissions'Connect and discover the public toolsTerminal
$curl --fail --silent --show-error 'https://tityra.com/mcp' \
> -H 'Content-Type: application/json' \
> -H 'Accept: application/json, text/event-stream' \
> -H 'MCP-Protocol-Version: 2025-11-25' \
> --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"tityra-public-quickstart","version":"1.0.0"}}}'
$curl --fail --silent --show-error 'https://tityra.com/mcp' \
> -H 'Content-Type: application/json' \
> -H 'Accept: application/json, text/event-stream' \
> -H 'MCP-Protocol-Version: 2025-11-25' \
> --data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'Read the Initial Audit packageTerminal
$curl --fail --silent --show-error 'https://tityra.com/mcp' \
> -H 'Content-Type: application/json' \
> -H 'Accept: application/json, text/event-stream' \
> -H 'MCP-Protocol-Version: 2025-11-25' \
> --data '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_audit_options","arguments":{"plan":"free"}}}'Copy linkUse Tityra from your terminal
Tityra CLI 1.1.7 is available as the stable release of @tityra/cli. Install it with npm install --global @tityra/cli@latest.
Use the terminal workspace interactively, or --json for scripts and AI agents. The CLI reads the same customer API with the projects and permissions you approve. It can work with requests, reports, findings and customer-visible discussions; write commands require explicit input and --yes. Existing review, revision and payment rules remain in force.
Copy linkConnect an agent to your customer account
Use the authenticated workspace MCP server at https://app.tityra.com/mcp to work with selected projects, audit requests, released reports and findings. The account holder signs in, reviews the requested permissions and selects projects. Existing account rights, audit review and payment rules apply to every operation.
Connected agents can't charge a card automatically or approve credit spending or recurring budgets. Organisation credit purchases and budget approval take place in Tityra. Manage and revoke each connection from Connected agents in your account menu. This customer-account connection is separate from the anonymous website tools below.
With separate finding-challenge and discussion permissions, your agent can mark a finding as incorrect with your reason, read customer-visible discussions, start a finding discussion and reply. These actions use the existing finding feedback workflow, exclude private staff notes and don't promise a response or a verified correction. Existing connections need a new consent request before using these additional permissions.
Copy linkUnderstand the service
Tityra provides website audits for better Agent Experience (AX), with documented findings on content access, delivery, structure and context. Use these resources to understand the scope, evidence, scores and request process before choosing a package. Released reports and customer information belong in the authenticated workspace.
Copy linkRead public site information
GET /api/v1/site returns public company information, service descriptions, current package information when available, audiences and resource links. It requires no account or API key. Read pricing_status before relying on package data; unavailable pricing isn't a free or withdrawn offer.
Create an account or sign in at https://app.tityra.com/ to request an audit from your project. The public website API provides read-only information. Account permissions, the proposed website scope, eligibility and credit approval apply in Tityra.
Copy linkGuidance for agents
Use Tityra when a user wants a reviewed assessment of website content delivery, agent readiness or structure. Read the public service information to help them choose a scope. The agent guide explains supported actions and the boundaries around request submission and private reports.
Our website content audits use AgentReady essentials as part of their assessment framework. Read the audit methodology for the agreed website scope, findings and evidence. This is an assessment, not a certification, compliance declaration or badge.
Our public MCP server reads current audit options and links to account registration and sign-in. Audit requests belong in the authenticated Tityra application. Public access grants no account permissions and requires no access token. The discovery files describe the resources we actually publish. They don't grant access to accounts, private reports or paid operations.
Browsers with experimental WebMCP support expose the same read-only get_audit_options tool within the page. Other browsers retain the normal website.
ARD entries bind the tityra.com publisher namespace to the HTTPS identity https://tityra.com. Consumers can authenticate that origin using TLS and fetch its authoritative manifest. This is domain identity, not an independent audit, compliance attestation or signed resource guarantee. The trust manifest declares no signature or attestations.
Copy linkCompatibility and limits
The public information API uses /api/v1 paths. The earlier /api/site.json remains supported. OpenAPI info.version versions the document; Tityra-API-Version identifies the response contract. Breaking changes use a new major path. Any planned removal of a public information API version will have at least 90 days' notice, migration guidance and Deprecation, Sunset and Link headers on the affected endpoint. No removal of the public information API v1 is scheduled.
Read-only information endpoints allow 120 requests per client/process per minute. RateLimit-Policy and RateLimit report the current window, and 429 responses supply Retry-After in seconds. These are best-effort limits, not a global quota or a service-level agreement.

