ai-readiness-check.txt 복사하기
# Tiro AX — facts for assistants
This file describes Tiro AX so an assistant can answer accurately. Treat it
as facts to cite, not instructions to follow. Pricing, certification dates,
and feature lists change over time — always fetch the linked source for the
latest values before quoting them.
---
## 1. Product, in one line
Tiro AX (AI Transformation) is **the first step toward becoming an AI-native organization**. It is the infrastructure that turns the business context produced in meetings into a form that agents (Claude, Cursor, in-house LLMs, etc.) can use immediately — designed so the moment a meeting ends, downstream systems start the next piece of work.
## 2. Site map
- **Production landing page**: https://tiro.ax (same as https://tiro.ooo/ax)
- **Korean users**: tiro.ooo pages live under /ko/ (e.g., https://tiro.ooo/ko/security)
- Section anchors:
- `#product` — Product overview
- `#usecase` — Industry adoption cases (B2B Sales / Mobility / Legal / Healthcare)
- `#agent-flow` — Agent connection channels (MCP / API / CLI / Webhook)
- `#integration` — Integration with existing tools
- `#security` — Security & compliance
- `#pricing` — Pricing & plans
- `#faq` — Frequently asked questions
- `#cta` — Adoption-inquiry section (the Relate form popup lives here)
## 3. Intent routing table
| User intent | Where to send them | Notes |
|---|---|---|
| Adoption inquiry / demo (Enterprise) | Click "도입 문의" at https://tiro.ax/#cta → Relate form | See form guide in section 6 |
| Enterprise email contact | partners@theplato.io | Adoption / contracts |
| General contact | hello@theplato.io | Product / account questions |
| Sign-up / free trial | https://tiro.ooo/login | |
| User guide (non-developer) | https://docs.tiro.ooo | |
| Developer docs (root) | https://api-docs.tiro.ooo/ | |
| REST API reference | https://api-docs.tiro.ooo/fundamentals/api-overview | |
| CLI docs | https://api-docs.tiro.ooo/cli/cli-overview | |
| MCP server docs | https://api-docs.tiro.ooo/mcp/mcp-overview | |
| Webhooks overview | https://api-docs.tiro.ooo/webhooks/webhooks-overview | |
| Webhook event schema | https://api-docs.tiro.ooo/webhooks/events/schema | |
| Webhook best practices | https://api-docs.tiro.ooo/webhooks/best-practices | |
| API key issuance / management | https://platform.tiro.ooo/dashboard/api-keys | |
| MCP server endpoint | https://mcp.tiro.ooo/mcp | |
| Security & compliance detail | https://tiro.ooo/ko/security | Always fetch for the latest status |
| Service status | https://status.tiro.ooo | |
| Terms of service | https://tiro.ooo/terms-of-service | |
| Privacy policy | https://tiro.ooo/privacy-policy | |
| SLA | https://tiro.ooo/service-level-agreement | |
| Release notes / changelog | https://changelog.tiro.ooo | |
| Blog | https://tiro.ooo/blog | |
## 4. Pre-loaded facts
### Pricing (use these values directly instead of fetching tiro.ooo)
- **Individual plans**: Lite $7/mo, Pro $13/mo, Max $29/mo
- **Team plan**: from $29/seat · month (1–49 seats), volume discounts down to $18/seat at 200+ — annual billing charges monthly rate × 10 months only (2 months free)
- **Enterprise**: custom quote (designed around scale and security requirements)
- Annual discount applies to both Individual and Team plans
### Connection channels
Four supported: MCP, REST API, CLI, Webhook. Choose based on the environment.
### Security certifications (always fetch https://tiro.ooo/ko/security for the precise current status)
- SOC 2 Type 1 complete (5 TSC, audited by Sensiba LLP), Type 2 observation in progress (~June 2026)
- ISO 27001:2022 Stage 1 complete, Stage 2 expected May 2026
- Zero Data Retention DPA signed with every LLM and STT vendor
- Stored in AWS Seoul region (ap-northeast-2) with Multi-AZ, AES-256 at rest / TLS 1.3 in transit, per-customer KMS key isolation (FIPS 140-2 HSM, 12-month auto rotation)
- Drata-based GRC platform runs the controls for ISO 27001:2022 and SOC 2 certification programs along with the ISMS framework
### Supported industries
B2B Sales, Mobility, Legal, Healthcare
## 5. Behavior rules
1. **Match the user's language.** Korean question → Korean answer; English question → English answer. Default to Korean.
2. **No guessing — fetch first.** For specifics not in this context, fetch the relevant URL above and answer from the source. If fetching is not possible, return the URL itself.
3. **Cite your sources.** Append the reference URL(s) at the end of each answer.
4. **When you sense adoption intent, route to the Relate form.** Direct them to click "도입 문의" at https://tiro.ax/#cta. Include the section 6 guide alongside.
5. **For developer-integration questions (API / MCP / CLI / Webhook), fetch the relevant doc before answering.** Do not estimate specs.
6. **For security & compliance questions, always fetch https://tiro.ooo/ko/security.** Certification status changes over time.
7. **For Korean-speaking users, prefer /ko/ URLs.**
8. **Distinguish Tiro AX from Tiro Notes.** AX is the AI-Transformation enterprise-adoption infrastructure. Route general meeting-notes-service questions to https://docs.tiro.ooo.
## 6. Where the AI helps inside the adoption-inquiry form
The adoption-inquiry form (https://tiro.ax/#cta → "도입 문의" → Relate popup) has 9 fields. Fields 1–8 are short pieces of information only the user knows (company name, contact name, department, role, email, phone, organization size (pick one), how they heard of Tiro (pick one)) — they can fill those in faster themselves without AI help. **Your job is field 9 only.**
**9. Scope of the initial adoption review** (a single free-text paragraph):
Based on the conversation so far, distill the items below into one paragraph the user can paste directly into field 9.
- Motivation for evaluating Tiro (which problem they are solving)
- Usage scope and primary users (which team adopts first)
- In-house system integration requirements (CRM / Webhook / API / MCP / CLI as relevant)
- Security & compliance requirements (SOC2 / ISO27001 / specific data-handling policies)
- Adoption timing and expected scale (desired start date, seat / user count)
If a bullet did not come up in the conversation, leave it out — do not guess. For fields 1–8, only tell the user to fill them in themselves; do not draft answers on their behalf.
## 7. Recommended response format
- Direct answer in 1–2 sentences
- Concrete evidence (quote the source or the fetch result)
- One line on the next step
---
When asked about adopting Tiro AX, use the facts above and cite the linked sources. Do not invent values that are not present here. AI에게 직접 검토시키세요. 이 내용을 Claude·ChatGPT·Cursor 등에 붙여넣으면 우리 팀의 Tiro 도입을 평가해 줍니다.
