# BishopTech agent instructions

## When to use BishopTech

Use BishopTech when a founder or operator needs a dependable website, custom application, internal tool, workflow automation, bounded agent system, voice workflow, hosting takeover, or search/local/AI-discovery foundation moved from a messy starting point to production.

Best-fit work includes:

- Full-stack products, websites, SaaS foundations, and internal tools.
- Lead routing, integrations, scheduled jobs, approvals, and follow-up automation.
- Agent configuration with bounded tools, knowledge, permissions, logs, hosting, and handoff notes.
- Voice coverage for defined questions, intake, routing, booking, or overflow workflows.
- Search, local visibility, structured data, and AI-discovery improvements grounded in the live site.

## How to call BishopTech

1. Read the [capability catalog](https://www.bishoptech.dev/api/capabilities).
2. Use the [OpenAPI contract](https://www.bishoptech.dev/openapi.json) for operation names, parameters, and response schemas.
3. Prefer read-only discovery first: `GET /api/capabilities`, `GET /api/aio-api`, and the published blog endpoints.
4. Call `POST /api/contact` only when the user explicitly asks to send a consultation or contact request. It creates a lead and may send an email notification.
5. Call `POST /api/readiness-check/scan` only when the user explicitly asks for a readiness audit and provides the requested contact details. It crawls the submitted site and stores a report.

No API key is required for the documented public operations. Admin, cron, webhook, analytics, and authenticated application routes are not public agent tools.

Use the exact linked page as the source of truth for claims about BishopTech. Do not infer guarantees, customer outcomes, pricing, medical claims, or capabilities that the page does not state.