Customer Agent Integrations

Overview / Purpose

Customer agents can help staff inspect product docs, retrieve visible football context, summarize cited information, and prepare controlled downstream work.

Customer agents work within the access your staff has approved. They use supported connections and respect service-account scope, staff permissions, plan access, record state, and rate limits.

Use this page to understand approved access before choosing an integration.

AI-provider workflows are not available at launch. An API or CLI key does not give permission to send private football data to OpenAI, Anthropic, Codex, Claude, ChatGPT, a plugin, or another AI provider. HotRoute's own agents are planned. External-agent and plugin connections remain planned or private-preview features.

Who this is for

This page is for organization owners, football operations leads, analysts, and approved technical partners.

In football terms, this is for the person deciding whether an outside agent should help a staff search docs, cite playbook context, retrieve schedule information, render a callsheet, or prepare a controlled workflow without taking over coaching judgment.

What to know first

Agent access is scoped access. The owner decides which organization, team, season, object families, and operation classes the tool can use.

Agent answers should cite their sources and show whether they used product docs, visible private football records, or both.

An agent may help retrieve, search, explain, draft suggestions, or prepare work where an approved route supports that job. It must not review, publish, archive, manage billing, manage members, rotate service-account keys, or act as a support or platform administrator.

Available API and CLI connections require a scoped service account. Other connections may be private-preview or planned; check the status below before choosing a tool.

Connections and availability

Service-account API client

Available where your organization owner has created a scoped service account and the API route is available. A client can call /api/v1 routes within that account's scope.

The key cannot be used as a staff login, retrieve hidden records, or access another organization, team, or season outside its scope.

Product-doc search agent

Beta where product-doc search is enabled for approved signed-in users or service accounts. It can retrieve HotRoute docs citations and explain product concepts.

Product docs do not contain your private playbook. The agent must not use them to guess private football information or hidden records.

Private football search agent

Beta or private-preview, depending on your plan, add-on, credits, and approved scope. It can search visible private football records and cite the sources it finds.

It cannot search records outside that access or return hidden information without citations.

Codex, Claude, or ChatGPT workflow

Planned. AI-provider use is not available at launch.

Once an approved connection is available, it could call supported API routes through a scoped service account and summarize cited results. Suggestions would still need staff review. Keep keys in secure storage and use only approved routes.

MCP adapter

Planned or private-preview. AI-provider use is not available at launch.

An approved adapter would connect through supported HotRoute routes. It must keep credentials narrow and respect the same access limits as the service account.

hot CLI from hotroute-tools

Available for approved service-account API use when your organization owner has created a scoped key and you have installed the signed CLI. It can inspect resource information, retrieve records, run supported searches, and make supported changes.

Its operations must stay within your organization, visibility, plan, and service-account scope. Record state and rate limits also apply.

User-consented OAuth connection

Planned. This would let a user authorize a tool to act within their own access, with consent, revocation, and an activity record.

A service-account key represents the organization integration; it does not represent an individual coach's permission.

Connect an available tool

For available API and CLI connections, start with Service Accounts and Install the hot CLI.

Before connecting a tool, confirm its available operations and service-account scope with your organization owner. Keep keys in secure storage and keep private football data inside the approved connection. AI-provider connections remain unavailable at launch.

What good looks like

A healthy customer-agent workflow feels like a careful staff assistant, not an autonomous coach.

The agent should:

• name the source it used
• distinguish product docs from private football records
• include useful citations or record references
• ask for missing team, season, playbook, or object scope instead of guessing
• refuse when scope, plan, record state, or rate limits do not allow the request
• route final football judgment back to the staff
• keep the service-account key narrow and revocable

Common questions or mistakes

Can an agent use product docs to answer questions about our private playbook?

No. Product docs explain HotRoute behavior. Private football questions need access to private football records, approved scope, and cited visible objects.

Can an agent publish changes for us?

No. Customer-agent access does not grant review, approval, publish, archive, billing, membership, support-admin, or platform-admin authority.

Can an MCP adapter use another access path?

Customer-visible adapters should call governed /api/v1 routes or another approved customer access path. Unpublished commands are not the customer access path.

Which records can the hot CLI change?

Only records and operations supported by the available API routes and your service-account scope. Organization, plan, visibility, record-state, and rate-limit restrictions still apply.

What should an agent do when HotRoute refuses a request?

It should report the refusal category plainly, avoid guessing hidden state, and ask the owner or staff operator to adjust scope only when broader access is appropriate.

Related docs / next steps

Start with Manage Service Accounts to create, review, revoke, or delete scoped keys.

Use Install the hot CLI when the approved agent will connect through the HotRoute command-line tool.

Use External API to understand which resource families an approved service account can call.

Use Retrieval and Search to understand how answers cited from product docs and private football records should behave.