NEWTON’SAPP AND AGENT DIRECTORY
The tools people build with
become the distribution layer.
OpenRouter turns apps and agents into a public ecosystem with rankings and attribution. Newton’s full version should support the same gravity: coding agents, IDEs, SDKs, agent frameworks, and builder platforms.
App and agent directory.
Start with compatibility, then add opt-in attribution and usage rankings once real traffic exists.
| App | Category | Newton’s fit |
|---|---|---|
| Claude Code | Coding agent | Agentic coding tool for repository reading, planning, editing, testing, and iteration. |
| Cursor | IDE | AI-native editor workflows that benefit from base URL, key, and model portability. |
| Cline | Coding agent | Open-source coding agent for IDE automation, terminal execution, and browser workflows. |
| Kilo Code | Coding agent | Agentic development across editors and CLI workflows. |
| OpenAI SDK | SDK | The simplest Newton’s integration path: change the base URL and key. |
| Vercel AI SDK | SDK | Application builders who need model routing, streaming UI, and predictable prepaid spend. |
| LangChain | Framework | Agent and chain orchestration across model providers. |
| Replit | Builder platform | Idea-to-app workflows where model access should stay portable. |
Full-app UX target.
Every integration should have a page with setup steps, supported models, known limits, spending policy, and receipt behavior. Later, opt-in apps can rank by usage and growth.