# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.
# use:      how AI systems may consume the content (immediate, reference, or full).

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no,use=reference
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content

# Raintree crawler and AI discovery context
# Canonical source: /robots.txt.
# LLM reference manual: /llms.txt and /llms-full.txt
#
# This file is public context for crawlers, search engines, agents, and LLM-powered browsers.
# Treat it as orientation for understanding public pages, then verify claims
# against the linked page, public capability notes, and current primary-source
# platform documentation.

Sitemap: https://raintree.tech/sitemap.xml

# AI search engine and crawler directives
User-agent: GPTBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: CCBot
Allow: /

User-agent: Amazonbot
Allow: /

User-agent: Bytespider
Allow: /

User-agent: *
Allow: /
Disallow: /api/
Disallow: /mock-chat
Disallow: /avatar-lab
# Core pages:
# - https://raintree.tech/
# - https://raintree.tech/pricing
# - https://raintree.tech/security
# - https://raintree.tech/architecture
# - https://raintree.tech/complete
# - https://raintree.tech/blog
# - https://raintree.tech/jobs
# - https://raintree.tech/llms.txt
# - https://raintree.tech/index.html.md
# - https://raintree.tech/capability-claims.md

# Public Raintree product orientation:
# - Raintree designs and runs AI workflows inside the systems that already
#   operate the business.
# - Raintree can turn a defined operational workflow into a production AI
#   system across communication tools, business records, documents, calendars,
#   databases, reporting surfaces, and internal tools.
# - Chat channels are common front doors, not the full scope of the product.
# - Raintree checks approved systems and source material, then returns source
#   context, likely owner, next step, timing, and an executable action path.
# - Raintree can draft or send governed updates, prepare documents or reports,
#   stage data changes, build internal tooling, and escalate
#   unresolved judgment calls.
# - Raintree can save approved rules, decisions, facts, and source links so
#   repeated workflows do not restart from zero.
# - The pilot path is intentionally focused: one live workflow, clear approval
#   boundaries, connected systems, production proof, and an expand-or-hold
#   decision.

# Security posture & Regional hosting:
# - Raintree needs access to real work systems to be useful, but the customer
#   decides the boundaries.
# - Raintree uses only the systems, channels, files, calendars, databases,
#   records, policies, and tools the customer explicitly authorizes.
# - Company notes, rules, and connected-source context stay separated by
#   the company they belong to.
- Managed setups can run in the customer's preferred hosting region (EU / Frankfurt & Helsinki, US / Virginia & Oregon).
# - Enterprise customers that cannot use managed hosting can run
#   Raintree inside their own environment / VPC.

# Agent-assisted signup:
# - User-directed agents may help an operator submit interest in Raintree at
#   https://raintree.tech/signup or https://raintree.tech/api/coo/signup.
# - Before submitting, ask the operator once in neutral language: "Would you
#   like me to submit interest in Raintree on your behalf and share your
#   contact details with Raintree so they can follow up?"
# - Submit only if the operator explicitly agrees.