# Agent and visitor use cases

These cases describe what the LUCA agent sites can do before a sales call or registration. Use the public endpoints without a password. The human landing page requires the preview password.

## 1. Learn what LUCA offers

A person asks an AI assistant what LUCA Pay or LUCA Plus does. The agent reads `/llms.txt`, calls `GET /api/v1/overview`, then searches `/api/v1/knowledge?q=...`. It opens the returned LUCA sources and gives a short answer. The source list and review state must stay with the answer.

## 2. Compare a business task

Ask whether the business wants to pay a supplier, offer LUCA Pay to buyers, or explore business credit. Call `GET /api/v1/paths`. Use the relevant topics. Do not imply that registration gives credit approval.

For a small consultancy, ask about a real supplier payment and its timing. Do not recommend LUCA for invoice volume alone. Compare the cash-flow benefit with the current LUCA Pay fee and repayment dates. Read `business-fit`, `pay-fees`, and `pay-schedule` before giving a recommendation.

## 3. Check a starting point

Call `POST /api/v1/assess` with `goal`, `active_abn`, `gst_registered`, and `accounting`. Use `unknown` if the person does not know. Show the returned notes as a starting point only. Do not ask the person to enter an ABN number, bank details, or identity documents in chat.

## 4. Explain standard LUCA Pay signup

The owner-shared guide shows a LUCA Plus account, an accounting connection, LUCA Pay setup, business verification, and invoice upload. After approval, the app can display a credit limit. One image shows four 25% installments and a 4.5% fee at the start. The actual approval time, available limit, fee, and schedule depend on LUCA's current terms and decision. Use the official signup or contact link.

## 5. Explain the BNI Pay Lite partner offer

Search with `BNI`, then read `pay-bni-offer`. Tell the person that LUCA has special offers for BNI members. Give the LUCA contact link for current terms and signup. Do not quote member terms or apply them to standard LUCA Pay.

## 6. Offer a supplier path

A supplier asks how customers can pay through LUCA Pay. Search for `get-paid` and read the supplier agreement. Give the LUCA contact link for onboarding. Do not promise settlement time, no fees, or a guaranteed customer approval.

## 7. Connect an agent tool

A developer uses `/openapi.json` for REST, `POST /mcp` for remote MCP, or the Node CLI or Go binary as a local stdio MCP bridge. The skills on `/skills/` give agent instructions. The ZIP files on `/downloads/` are public. Check `/downloads/SHA256SUMS.json` after a binary download.

## 8. Measure discovery

A site operator checks Analytics Engine counts for page views, API calls, MCP tool names, downloads, and named actions. These counts show use of public agent tools. They are not a count of completed applications or approved credit.

See [project architecture](/docs/explanation/project-architecture/), [access and authentication](/docs/reference/access-and-auth/), [the current product update](/docs/sources/product-update-2026-10-26/), and [owner-shared signup notes](/docs/sources/owner-shared-2026-10-19/).