kopia lustrzana https://github.com/transitive-bullshit/chatgpt-api
![]() |
||
---|---|---|
.cursor/rules | ||
.github | ||
.vscode | ||
apps | ||
packages | ||
.editorconfig | ||
.gitignore | ||
.npmrc | ||
.prettierignore | ||
eslint.config.js | ||
license | ||
package.json | ||
pnpm-lock.yaml | ||
pnpm-workspace.yaml | ||
readme.md | ||
tsup.config.ts | ||
turbo.json |
readme.md
Agentic
API Gateway
- REST:
GET/POST gateway.agentic.so/deploymentIdentifier/toolName
- => MCP:
MCPClient.callTool
with JSON body parameters - => OpenAPI:
GET/POST/ETC originUrl/toolName
operation with transformed JSON body params
- => MCP:
- MCP:
mcp.agentic.so/deploymentIdentifier
MCP server?- => MCP:
MCPClient.callTool
just proxying tool call - => OpenAPI:
GET/POST/ETC originUrl/toolName
operation with transformed tool params
- => MCP:
- RAW:
METHOD gateway.agentic.so/deploymentIdentifier/<pathname>
- => Raw HTTP:
METHOD originUrl/<pathname>
simple HTTP proxy request - TODO: remove / disable
raw
support for now
- => Raw HTTP:
TODO
- webapp
- stripe
- stripe checkout
- stripe billing portal
- end-to-end working examples
- openapi
- mcp
- raw
- auth
- custom auth pages for
openauth
- custom auth pages for
- API gateway
- usage tracking and reporting
- oauth flow
- openapi-kitchen-sink
- mcp-kitchen-sink
- how to handle binary bodies and responses?
- improve logger vs console for non-hono path and util methods
- extra
Sentry
instrumentation (setUser
,captureMessage
, etc)
- Public MCP server interface
- how does oauth work with this flow?
- proper error handling support within this flow; will currently get generic errors
- Origin MCP servers
- how to guarantee that the request is coming from agentic?
_meta
for tool calls- still need a way of doing this for initial connection requests
- mcp auth provider support
- binary bodies / responses?
- resources
- prompts
- other MCP features?
- how to guarantee that the request is coming from agentic?
TODO Post-MVP
- first-party deployment hosting
- api gateway stress tests
- auth
- custom auth provider configs for projects/deployments
- stripe
- re-add coupons
- declarative json-based pricing
- stripe connect
- stripe-related billing emails
- re-add support for teams / organizations
- consider switching to consola for logging?
- consider switching to
bun
(for--hot
reloading!!) - validate stability of pricing plan slugs across deployments
- same for pricing plan line-items
- replace
ms
package - API gateway
- do I just ditch the public REST interface and focus on MCP?
- SSE support? (no; post-mvp if at all; only support streamable http like smithery does, or maybe support both?)
- signed requests
- add support for custom headers on responses
- add ability to only report stripe usage on non-cached requests
- add support for ToolConfig.cost defaulting to 1, to easily support tools which cost multiple "credits"
@agentic/platform-hono
- additional transactional emails
- consider
projectName
andprojectSlug
orprojectIdentifier
? - handle or validate against dynamic MCP origin tools
- allow config name to be
project-name
or@namespace/project-name
? - upgrade to zod v4
License
UNLICENSED PROPRIETARY © Agentic
To stay up to date or learn more, follow @transitive_bs on Twitter.