Agent Utilities

Agent developers

Catch configuration mistakes before a run

Missing environment variables and confusing tool names can break an otherwise working agent. Check these deterministic details before starting a long run.

$0.0016 for one successful call to each of the 3 tools below.

01

Compare environment-variable names

Supply a template and configuration to find missing, extra and duplicate variable names. Values are not returned. Prefer sanitized assignments when checking names; real credentials are unnecessary.

agents.env-template-check · $0.0005 per call ↗
02

Find ambiguous tool names

Check a combined tool catalog for duplicate names and collisions after Unicode, case and separator normalization. A conflict is a prompt to review naming, not proof of a client failure.

agents.tool-name-conflicts · $0.0003 per call ↗
03

Review explicit risk indicators

Apply five fixed heuristics to configuration text. Findings identify matched language for review. They cannot certify that an agent is safe or enforce its permissions.

agents.config-audit · $0.0008 per call ↗

What you get

A short list of concrete configuration issues to review before execution. Keep permission enforcement and credential storage in your own runtime.

These are separate API calls that your agent orchestrates, not an automatic bundled workflow. Review each tool's example and contract; input fields must be mapped explicitly between steps.

A small first step

Pick a useful tool.
Give it a real task.

Review its example and price, then create an API key and save your recovery key. Add $5 in service credits through Stripe and call the API from your agent.