Ajax Davis 300083aff9 refactor(executor): switch vercel template from Next.js to Deno runtime

- Replace Next.js app router with pure Deno API functions
- Use vercel-deno@3.0.0 community runtime for native HTTP imports
- Deno natively supports importing from esm.sh URLs
- Simplified template: just api/health.ts and api/execute-tool.ts
- Remove unnecessary React/Next.js dependencies
- Update README with new architecture documentation

This matches the Railway executor's Deno-based approach but runs on
the user's own Vercel account. The Deno runtime enables dynamic
imports from esm.sh without any special setup.

2026-01-09 01:15:47 +10:00

4 KiB

Raw Blame History

TPMJS Executor for Vercel

Deploy your own TPMJS tool executor using the Deno runtime on Vercel for secure, isolated code execution.

Features

Native HTTP Imports: Deno natively supports importing from esm.sh
Full Control: Your infrastructure, your environment variables
Privacy: No data passes through TPMJS servers
One-Click Deploy: Deploy to Vercel in minutes

One-Click Deploy

How It Works

This executor uses the Vercel Deno Runtime to:

Receive tool execution requests via POST /api/execute-tool
Dynamically import the npm package from esm.sh (Deno natively supports HTTP imports!)
Execute the tool with your parameters
Return the result

This provides the same execution model as the Railway executor, but deployed to your own Vercel account.

API Endpoints

GET /api/health

Check executor health status.

curl https://your-executor.vercel.app/api/health

Response:

{
  "status": "ok",
  "version": "1.0.0",
  "info": {
    "runtime": "deno",
    "httpImports": true,
    "timestamp": "2024-01-01T00:00:00.000Z"
  }
}

POST /api/execute-tool

Execute a TPMJS tool.

curl -X POST https://your-executor.vercel.app/api/execute-tool \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer your-api-key" \
  -d '{
    "packageName": "@anthropic-ai/tpmjs-hello",
    "name": "helloWorld",
    "version": "latest",
    "params": { "name": "World" }
  }'

Response:

{
  "success": true,
  "output": "Hello, World!",
  "executionTimeMs": 234
}

Configuration

Environment Variables

Variable	Required	Description
`EXECUTOR_API_KEY`	No	API key for authentication. If set, requests must include `Authorization: Bearer <key>` header.

Add custom environment variables for your tools (e.g., MY_API_KEY, DATABASE_URL) in your Vercel project settings.

Setting Up API Key Authentication

Go to your Vercel project settings
Add an environment variable: EXECUTOR_API_KEY with a secure random value
When configuring your executor in TPMJS, enter this key in the "API Key" field

Connecting to TPMJS

Go to your TPMJS collection or agent settings
In "Executor Configuration", select "Custom Executor"
Enter your executor URL: https://your-executor.vercel.app
Enter your API key (if configured)
Click "Verify Connection" to test

Local Development

# Install Vercel CLI
npm install -g vercel

# Login to Vercel
vercel login

# Run development server
vercel dev

# Test the health endpoint
curl http://localhost:3000/api/health

Note: Local development requires the Vercel CLI. Run vercel login first.

Security

Set EXECUTOR_API_KEY to require authentication for all requests
Tools are loaded dynamically from esm.sh
Each request gets fresh environment variable injection
CORS headers allow cross-origin requests (configurable)

How It Compares to TPMJS Default Executor

Feature	TPMJS Default (Railway)	Your Vercel Executor
Runtime	Deno on Railway	Deno on Vercel
Cost	Free (TPMJS hosted)	Your Vercel usage
Env Vars	Stored in TPMJS	Stored in your Vercel project
Privacy	Requests go through TPMJS	Direct to your executor
Control	Managed by TPMJS	Fully yours

Pricing

Vercel's free tier includes generous limits for serverless functions. See Vercel Pricing for details.

4 KiB Raw Blame History