pi-requesty-discover
Discover available Requesty models for the Pi Coding Agent
Package details
Install pi-requesty-discover from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:pi-requesty-discover- Package
pi-requesty-discover- Version
1.0.6- Published
- Jul 15, 2026
- Downloads
- 1,087/mo · 165/wk
- Author
- enolive
- License
- MIT
- Types
- extension
- Size
- 30.6 KB
- Dependencies
- 1 dependency · 2 peers
Pi manifest JSON
{
"extensions": [
"./index.ts"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
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_KEYfrom the environment - Health-check available models and write a log about them
- Provide a dry-run mode that does not change anything
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 the list to complain about non-working models via a dry-run
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 fetches Requesty models using ~/.pi/agent/models.json and writes the discovered model IDs back to the same file.
Run /reload after syncing.
/requesty-discover --dry-run
This will not overwrite the models.json file, but will do everything else, including the health checks.