pi-requesty-discover

This extension helps you discover currently available models in requesty.ai for your Pi Coding Agent.

This is a fork of pi-requesty with additional features:

• Use REQUESTY_API_KEY from the environment
• Health-check available models and write a log about them
• Brief information about what was found, including added/removed models, health summary
• Confirm before writing models.json, with a dry-run mode that only previews
• A footer status line showing your monthly Requesty spend against your monthly limit

When and why use it

Use this extension if

• you are on Requesty.ai
• you are limited to certain models by a company policy (for instance, for data residency/protection reasons)
• you don’t want to handcraft your own curated list of models constantly
• you want to health-check models and preview the diff before writing
• you want to keep in touch with your usage without having to constantly visit the Requesty dashboard

Installation

# NPM
pi install npm:pi-requesty-discover
# GitHub
pi install git:github.com/enolive/pi-requesty-discover

Install locally

Check out the code from the official code repository https://github.com/enolive/pi-requesty-discover, and then:

pi install ./pi-requesty-discover

To run once without installing:

pi -e ./pi-requesty-discover

Configuration

The extension reads the requesty-export provider from ~/.pi/agent/models.json. You can override the provider id with the REQUESTY_PROVIDER_ID variable.

Example:

{
  "providers": {
    "requesty-export": {
      "name": "Requesty",
      "baseUrl": "https://router.requesty.ai/v1",
      "apiKey": "$REQUESTY_API_KEY",
      "api": "openai-completions",
      "models": []
    }
  }
}

❗ IMPORTANT
The apiKey from models.json is not used by this extension. It may contain Pi-specific environment-variable substitution that the extension cannot reliably resolve. Set REQUESTY_API_KEY instead. This variable is required. You can configure the real apiKey as you like, but it would be recommended to use the same variable as for the model discovery.

❗ IMPORTANT
Health checks are designed to use only a few tokens, but they still make real Requesty API calls and may consume credits.

On startup, the extension fetches <baseUrl>/models using REQUESTY_API_KEY as the bearer token and registers discovered and healthy models with Pi.

Environment variables

Name	Required	Type	Default	Meaning
REQUESTY_API_KEY	yes	string		Requesty API key used for model discovery and health checks.
REQUESTY_PROVIDER_ID	no	string	requesty-export	The id of the provider.
REQUESTY_HEALTH_CHECK_MODE	no	off, basic, full	full	The health-check mode.
PI_CODING_AGENT_DIR	no	string	~/.pi/agent	pi configuration directory

Command

Inside Pi:

/requesty-discover

The command:

• discovers Requesty models (and optional health checks)
• shows a summary notification (added/removed IDs, health summary)
• asks for confirmation before writing ~/.pi/agent/models.json
• reports whether the file was updated

If there are no model ID changes, confirmation still offers a metadata refresh write, which might have changed as well.

After a successful write, run /reload.

/requesty-discover --dry-run

Same discovery and health checks, but never prompts to write and leaves models.json unchanged.

Usage status

The extension shows your current Requesty monthly spend as a persistent line in Pi’s footer, e.g.:

Requesty Usage (<API Key Name>): $63.55/$150.00 (42%)

When your API key has no monthly limit (monthly_limit is 0), the limit is treated as unlimited:

Requesty Usage (<API Key Name>): $63.55 (unlimited)

When you select a model from a provider other than REQUESTY_PROVIDER_ID, the status is cleared — there is no Requesty usage to show for it. If REQUESTY_API_KEY is not configured, the status is left untouched.

📌 NOTE
The footer update is best-effort and never blocks a turn. If it fails (network error, stale context after /reload), it fails silently without spamming notifications.