Agent-ready service access

AI Agent Usage and Payment Guide

How personal assistants, browser agents, computer-use agents, coding agents, and workflow agents can discover BLUE GLORIOUS services, open the free AI script tool, read pricing, and route payment intent safely.

Autonomous agents may assist discovery, browser actions, and routing, but payment-sensitive actions require explicit human confirmation.

Open free AI script toolView pricing
01020304

How agents connect to BLUE GLORIOUS

Personal agents and workflow agents should connect through public pages and machine-readable discovery files, then hand control back to the user before any payment-sensitive step.

  • Supported agent types include personal assistants, browser agents, computer-use agents, coding agents, and workflow agents.
  • Discovery files: read /llms.txt, /robots.txt, /sitemap.xml, /.well-known/ai-services.json, and /.well-known/openapi.json before summarizing the service.
  • Free tool route: open /services/ai-script-rewrite for trial use, script preparation, rewrite, expansion, localization, diagnosis, and export.
  • Pricing route: open /pricing to read the latest plan names, limits, display currencies, and team or enterprise paths.
  • Contact route: open /contact for enterprise, BYOK, private deployment, human editing, invoices, or custom production requests.

How agent-assisted payment should work

  • The agent may compare plans, explain limits, and prepare a recommendation.
  • The agent may navigate to pricing, contact, or an authorized checkout page only after the user confirms intent.
  • The user must review plan, amount, currency, invoice details, and terms on the checkout, order confirmation, or company contract.
  • The agent must not enter payment details, approve contracts, or claim payment is complete without explicit human confirmation.

Recommended agent workflow

01

Discover

Read llms.txt, robots.txt, sitemap, and the machine-readable service directory.

02

Open tool

Route users to the AI Script Rewrite Workspace for free trial or source-script preparation.

03

Read pricing

Summarize plans, supported currencies, limits, and team or enterprise options.

04

Confirm

Ask for explicit user confirmation before directing the user to payment or contact.

05

Hand off

Send users to pricing, contact, or authorized checkout. Never claim payment is completed by the AI tool.

Payment Safety

Payment and subscription rules

The public website exposes pricing, contact, and payment-intent routing. It does not expose an autonomous payment API. Personal agents, browser agents, computer-use agents, coding agents, and workflow agents should treat paid actions as user-confirmed navigation, not background purchasing.

  • Human confirmation is required before paid-plan activation.
  • Final billing currency and invoice details are confirmed on checkout, order confirmation, or company contract.
  • Team, enterprise, BYOK, private deployment, and human editing requests should route to contact.
  • AI tools should preserve copyright, platform compliance, and user data warnings when summarizing the service.
1
2
3
4
5

What mature AI agents can do

  • Explain the rewrite, expansion, localization, diagnosis, and production-planning workflow.
  • Open the free workspace and help the user prepare source-script instructions.
  • Compare plans and supported display currencies.
  • Route confirmed commercial intent to pricing or contact.

What requires a human

  • Approving payment, subscription, invoice, or contract terms.
  • Uploading sensitive scripts or owned IP into the tool.
  • Final copyright review, platform review, and production approval.

Machine-readable files

Agent frameworks and AI assistants can use these public files to understand service scope, pricing display, multilingual routes, and crawler policy. Search crawlers and user agents may also use them for discovery.

llms.txtAI services JSONOpenAPIPricing
BLUE GLORIOUS: https://blueglorious.com/.well-known/ai-services.json