SubmitMetered MCP SaaS · Product · Live ↗

Submit — metered MCP SaaS for form automation

Camaleão's primitives, sold by the credit — JSON-RPC over HTTP/SSE with Stripe billing.

RoleArchitect & BuilderProtocol, metering, billing
TransportMCP / JSON-RPCHTTP + SSE, credit-metered
StackClaude · Camaleão · StripeResend · Postgres/Drizzle

The context

Camaleão is powerful infrastructure. Submit turns it into a product: a commercial MCP server that any agent can call, with usage metered and billed.

It speaks MCP over JSON-RPC (HTTP and SSE), wraps the browser primitives — goal-directed tasks, login, extraction, signup, form-fill — and gates them behind a credit-based quota with Stripe checkout and billing portals. Transactional email runs on Resend; CAPTCHA and proxy concerns inherit from Camaleão. It is the packaging layer that makes agent-driven form automation sellable.

What I built
Metered SaaSMCP ServerStripe BillingCredit QuotasJSON-RPC / SSEAuth & Keys
Stack
Anthropic ClaudeCamaleãoStripeResendPostgresDrizzleZodMCP

The interface

live in production
Submit — live interface

The model

primitives → product
   agent / customer
        │  MCP (JSON-RPC over HTTP + SSE)
        ▼
   ┌──────────────────────────────────┐
   │   Submit  ·  metered MCP server   │
   │   form-fill · login · extract    │
   │   signup · goal-directed tasks   │
   └──────────────────────────────────┘
        │  meter            │  execute
        ▼                   ▼
   Stripe credits        Camaleão primitives
   quota · billing portal   (browser, anti-bot)
Metered
Credit-based quota billed through Stripe checkout + portal.
MCP
JSON-RPC over HTTP and SSE — any agent is a customer.
Built on
Camaleão's browser stack does the real work.