Review the prompt pack
Generate the buyer questions mybrand.com should be visible for. Show them before running a visibility check.Codex / Agent Skill setup
Install Radar's workflow once, then ask Codex to audit AI readiness, generate buyer questions, measure brand visibility, check named products, and explain the evidence behind every result.
Install Radar globally for Codex and other compatible agents:
npx skills add optifeed/optifeed-radar --skill optifeed-radar -gStart a new Codex session, invoke $optifeed-radar, or describe the audit you want. The skill can run Radar through the CLI without any MCP configuration.
MCP adds five structured tools, progress reporting, and default non-interactive cost caps:
codex mcp add optifeed-radar -- \
npx -y --package=optifeed-radar@0.2.3 optifeed-mcpcodex mcp listUse /mcp in the Codex terminal UI to inspect the connection. The skill automatically prefers MCP when those tools are available.
Run a free AI-readiness audit on mybrand.com with Optifeed Radar.
Explain every finding and do not start a paid visibility check.The prompt maps to audit_store. It verifies the connection without an API key or AI-provider charge.
Generate the buyer questions mybrand.com should be visible for. Show them before running a visibility check.Check mybrand.com's AI visibility in quick mode. Use OpenAI only and cap total spend at $0.15.Check these products for mybrand.com: Product A, Product B. Explain absences and competitors. Cap total spend at $0.40.Radar does not import a catalog. It measures each supplied product against its own shopper questions; input order is not treated as a merchant ranking.
For paid checks, put the provider keys you use in a local .env file in the project where Radar runs, or forward selected environment variables through Codex configuration. Do not place real keys in prompts or commit them.
[mcp_servers.optifeed-radar]
command = "npx"
args = ["-y", "--package=optifeed-radar@0.2.3", "optifeed-mcp"]
env_vars = ["OPENAI_API_KEY", "ANTHROPIC_API_KEY", "GOOGLE_API_KEY", "PERPLEXITY_API_KEY"]Codex stores user-level configuration in ~/.codex/config.toml. Only include the variable names for providers you actually use.