Get started

Hyperise for AI agents

Hyperise personalizes images, videos, and websites at scale, letting sales and marketing teams add dynamic, prospect-specific elements to outreach so each message feels individually made. 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 HyperiseSee the 5 actions ↓
MarketingAPI keyMCP + RESThyperise.com
AUDIT LOG · HYPERISEPOLICY: acme-support
09:41:07 · claude · u_8f2read
hyperise.list_image_templates
List Image Templates✓ allowed · 212ms
09:41:09 · claude · u_8f2write
hyperise.create_client_account
Create Client Account✓ approved · approved by user
EVERY HYPERISE CALL, ON THE RECORD
01 · USE CASES

What agents do in Hyperise.

01

Generate a personalized link

Generate a personalized short link with a prospect's name and logo for an outreach email.

02

List available image templates

List image templates to pick one that fits a new outbound campaign's design.

03

Update prospect data before sending

Update a prospect's personalization data so a generated image reflects their latest company details.

02 · ACTIONS

5 Hyperise actions, graded by risk.

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

read

1

Look things up. Allowed by default.

  • hyperise.list_image_templates
    List Image Templates

write

4

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

  • hyperise.create_client_account
    Create Client Account
  • hyperise.user_authentication
    User Authentication
  • hyperise.prospect_business_data
    Hyperise Prospect Business Data (CRUD)
  • hyperise.personalized_short_links
    Generate Personalized Short Link

destructive

0

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

  • No destructive actions.
03 · HOW IT WORKS

Hyperise in three steps.

  1. 01Your users connect HyperiseThey add their Hyperise api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “create Client Account” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Hyperise 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('hyperise', {
  read: 'allow',
  write: 'ask',        // create_client_account
  destructive: 'deny',  
})

# 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 Hyperise connects.

Users add their Hyperise 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 Hyperise 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 Hyperise 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

Hyperise and Arc0, answered.

Q01

Can I use Hyperise with Claude, ChatGPT or Cursor?

Yes. Connect Hyperise 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 Hyperise actions you allow.

Q02

How do users connect Hyperise?

Users add their Hyperise 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 Hyperise actions can my agent take?

5 in total: 1 read, 4 write and 0 destructive, such as “create Client Account”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Hyperise?

Yes. Allow read actions and deny writes in the Hyperise policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Hyperise too?

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

Get started

Plug Hyperise into your agent.

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

Connect HyperiseBrowse all apps →

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