Get started

redirect.pizza for AI agents

redirect.pizza is a URL redirect manager for tracking domains, creating redirects, and generating QR codes for marketing links. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect redirect.pizzaSee the 14 actions ↓
MarketingAPI keyMCP + RESTredirect.pizza
AUDIT LOG · REDIRECT.PIZZAPOLICY: acme-support
09:41:07 · claude · u_8f2read
redirect_pizza.list_domains
List Domains✓ allowed · 212ms
09:41:08 · claude · u_8f2read
redirect_pizza.get_team
Get Team✓ allowed · 164ms
09:41:09 · claude · u_8f2write
redirect_pizza.create_redirect
Create Redirect✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
redirect_pizza.delete_redirect
Delete Redirect✕ blocked · policy: deny
EVERY REDIRECT.PIZZA CALL, ON THE RECORD
01 · USE CASES

What agents do in redirect.pizza.

01

Check a redirect before publishing

Look up an existing redirect's source and destination URL before changing where it points.

02

Create a new redirect

Set up a redirect from a purchased domain to a landing page or campaign URL.

03

Pause instead of deleting

Set a redirect or its source to paused rather than removing it outright, so traffic can resume later.

02 · ACTIONS

14 redirect.pizza actions, graded by risk.

Every redirect.pizza action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • redirect_pizza.get_team
    Get Team
  • redirect_pizza.get_domain
    Get Domain
  • redirect_pizza.get_redirect
    Get Redirect
  • redirect_pizza.list_domains
    List Domains
  • redirect_pizza.list_redirects
    List Redirects
  • redirect_pizza.check_domain_dns
    Check Domain DNS
  • redirect_pizza.test_redirect_url
    Test Redirect URL

write

6

Create and change things. Allow, or ask the user first.

  • redirect_pizza.create_redirect
    Create Redirect
  • redirect_pizza.update_redirect
    Update Redirect
  • redirect_pizza.upsert_redirect
    Upsert Redirect
  • redirect_pizza.generate_qr_code
    Generate QR Code
  • redirect_pizza.set_redirect_paused
    Set Redirect Paused
  • redirect_pizza.set_redirect_source_paused
    Set Redirect Source Paused

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • redirect_pizza.delete_redirect
    Delete Redirect
03 · HOW IT WORKS

redirect.pizza in three steps.

  1. 01Your users connect redirect.pizzaThey add their redirect.pizza api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Redirect” can wait for the user, and “delete Redirect” can be denied outright.
  3. 03Any agent can actYour agent calls redirect.pizza through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('redirect_pizza', {
  read: 'allow',
  write: 'ask',        // create_redirect
  destructive: 'deny',  // delete_redirect
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How redirect.pizza connects.

Users add their redirect.pizza api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same redirect.pizza connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use redirect.pizza from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More marketing apps.

Meta Ads67 actionsActiveCampaign298 actionsActiveTrail159 actionsAdobe Marketing Agent12 actionsAdtraction22 actionsAdyntel8 actionsAhrefs40 actionsAirOps96 actions
ALL MARKETING APPS →
07 · FAQ

redirect.pizza and Arc0, answered.

Q01

Can I use redirect.pizza with Claude, ChatGPT or Cursor?

Yes. Connect redirect.pizza to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the redirect.pizza actions you allow.

Q02

How do users connect redirect.pizza?

Users add their redirect.pizza api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which redirect.pizza actions can my agent take?

14 in total: 7 read, 6 write and 1 destructive, such as “create Redirect”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in redirect.pizza?

Yes. Actions like “delete Redirect” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call redirect.pizza too?

Yes. The same redirect.pizza connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug redirect.pizza into your agent.

Your users connect redirect.pizza once, under your brand. Your agent gets 14 actions behind your policies, with every call on the record.

Connect redirect.pizzaBrowse all apps →

Free to build · MCP + REST · Audit log on every plan