PipedreamHQ / PipedreamHQ/pipedream
[APP] The Grid
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Name of app / service**
The Grid — https://thegrid.ai
**Link to developer documentation**
https://thegrid.ai/docs — API reference at https://thegrid.ai/docs/api-reference/consumption-api
The Grid is an OpenAI-compatible inference marketplace. Auth is a bearer API key against `https://api.thegrid.ai/v1`, so the auth schema is the standard single `api_key` string, same shape as the existing `deepseek` and `cerebras` apps.
**Is lack of support preventing you from moving forward, or do you have a workaround?**
There is a workaround, but it's a poor one. The existing `openai` app hardcodes its base URL (`openai.app.mjs` returns `https://api.openai.com/v1` with no override prop), and `openai_passthrough` is auth-only, so there's no way to point Pipedream's OpenAI actions at another OpenAI-compatible endpoint. Today the only options are a generic HTTP Request action or a Node.js code step — both work, but they give no presence in the app directory and no MCP tool catalog entry.
**Are there specific actions or triggers you'd like to see for this app?**
I'd like to contribute the components myself, modeled on `components/deepseek/`:
- `create-chat-completion` — chat completions with tools/tool_choice, temperature, maxTokens, responseFormat, stream
- `list-models` — `GET /v1/models` (verified: returns a spec-shaped `{object: "list", data: [...]}`, currently 17 instruments)
I understand from the PR template and from #20981 that the app needs to be scaffolded on your side before a components PR can be reviewed — hence this request first. I work on The Grid, so I can answer anything about the API and provide test credentials for review.
Contributor guide
Research direction
Review components/deepseek/ and the existing openai and openai_passthrough app components to understand the expected scaffold and authentication shape. Check the documented The Grid endpoints and confirm that the scaffold supports the requested chat-completion and list-models components, with the specified actions and API-key authentication ready for review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100