Skip to main content

​
Overview

Type: Coding ToolPrimary Path: OpenAI-compatibleSupport Confidence: Supported path
Pi is a minimal terminal coding harness. In the LemonData docs IA, it belongs under Coding Tools, not under native SDKs. Pi is interesting because it sits between a classic CLI tool and an embeddable runtime:
  • interactive terminal coding workflow
  • JSON / RPC modes for process integration
  • SDK-style embedding into your own applications
For LemonData, Pi is usually easiest to configure through an OpenAI-compatible provider path, unless you intentionally want Anthropic-native or Google-native behavior. Use LemonData as an OpenAI-compatible endpoint: 
export OPENAI_API_KEY="sk-your-lemondata-key"
export OPENAI_BASE_URL="https://api.lemondata.cc/v1"
Then configure Pi’s provider or custom model settings so its OpenAI-style path points at LemonData.
Pi can also work with Anthropic-style and Google-style providers. If you want Claude-native or Gemini-native behavior, treat that as a provider-specific Pi setup rather than a generic OpenAI-compatible setup.

​
Why Pi Is Different

Pi is not just “another SDK”.
  • If you are using Pi as a terminal agent, evaluate it like a coding tool
  • If you are embedding Pi into your own app, evaluate it like an agent runtime / harness
That is why this page focuses on the practical LemonData connection path rather than calling Pi a pure SDK.

​
Practical Setup Notes

Start with LemonData’s https://api.lemondata.cc/v1 path unless your Pi workflow explicitly depends on a native provider protocol.
Claude-native or Gemini-native Pi setups should be documented and tested as separate provider-specific paths, not assumed to be identical to the OpenAI-compatible route.
Pi is highly configurable. LemonData can document the connection path, but not every extension, skill, or custom harness behavior should be treated as part of the compatibility contract.

​
Troubleshooting

  • Verify the configured OpenAI-style base URL is exactly https://api.lemondata.cc/v1
  • Verify the key starts with sk-
  • Verify the selected Pi provider path matches the protocol you intend to use
  • Keep the LemonData model id separate from any Pi-local aliasing
  • If you are testing provider-native behavior, confirm the Pi provider is really using that native path