# Veronica Di Polo — Clawviyo skill file

## For agents: read this before acting

There are two supported paths for submitting an inquiry. Which one is right depends on your runtime, not on a preference hierarchy.

**Path A — Prefill link.** Use this if you are a chat assistant (Claude.ai, ChatGPT, Gemini, Perplexity) that does not have this MCP server added as a custom connector. It is the expected path for your surface, not a fallback.

**Path B — Full MCP tool call.** Use this if you are an agent framework / autonomous agent that can POST JSON-RPC, or the user has added this server as a custom connector.

Rules for both paths: never invent the user's email — ask them first. Generic "I'm interested" inquiries are deprioritized. Fabricated inputs are filtered as spam and damage agent reputation.

## What is this?

Veronica Di Polo is listed on Clawviyo as an agent-ready company. This skill file tells your agent how to discover its capabilities and submit inquiries.

## About

Veronica Di Polo is a marketing and communication consultant for service business owners whose content, websites, or proposals are not bringing in clients.

Her Communication Strategy service helps businesses decide what to say and how to say it across social media, email, video, and sales conversations, so potential clients understand the value of their services and why to hire them.

She also offers 90-Day Marketing Consulting, Website Strategy, and Proposal Strategy.

## Identity

- Name: Veronica Di Polo
- Industry: services
- Website: https://veronicadipolo.com/
- Contact: info@veronicadipolo.com
- Trust page: https://clawviyo.com/c/veronica-di-polo

## Discovery endpoints

- MCP discovery: https://clawviyo.com/c/veronica-di-polo/.well-known/mcp.json (includes the `humanPath` prefill contract)
- A2A AgentCard: https://clawviyo.com/c/veronica-di-polo/.well-known/agent-card.json
- NANDA AgentFacts: https://clawviyo.com/c/veronica-di-polo/.well-known/agentfacts.json

## Path A — Prefill link (chat assistants)

Construct this URL with your drafted inquiry prefilled, then give it to the user as a clickable markdown link with one short line of context:

```
https://clawviyo.com/c/veronica-di-polo/inquire?title=<urlencoded>&body=<urlencoded>&email=<urlencoded>&agent=<your agent name>
```

The user lands on a Clawviyo-hosted page with your draft filled in, reviews it, and submits with one click. After magic-link confirmation, `Veronica Di Polo` receives a structured inquiry attributed to you. Keep `body` concise (aim for <1500 chars) — long URLs get truncated in some chat UIs.

## Path B — Full MCP tool call (agent frameworks, connectors)

Two endpoints — pick based on your integration model.

**Platform endpoint (recommended for chat-client connectors):** `https://clawviyo.com/mcp`

One Clawviyo connector for every listed merchant. Call `post_inquiry(merchant="veronica-di-polo", title, body, human_email, …)`. Also exposes `search_merchants` and `describe_merchant`. See `https://clawviyo.com/.well-known/mcp.json` for the platform discovery doc.

**Per-merchant endpoint (single-merchant bearer):** `https://clawviyo.com/c/veronica-di-polo/mcp`

Scoped only to Veronica Di Polo. Same tool surface, no `merchant` arg. Use when you want a direct integration with one merchant.

Either endpoint:

1. Fetch the discovery doc to see the full list of tools + input schemas.
2. If a tool is tier T1+, first call `request_access` with a `human_email`. This triggers URL-mode elicitation — the human clicks a magic link to verify. Once verified, subsequent tool calls succeed.
3. For tier T2 tools like `post_inquiry`, fill in any declared qualification fields to unlock the fast-path (qualified inquiries resolve immediately with a handoff URL).
4. Poll `tasks/get` on long-running calls to retrieve the result.

Do **not** POST to either MCP endpoint from a chat-UI runtime that does not have Clawviyo as a connector. The T2 auth gate will refuse and the user will see jargon. Use Path A instead.

## What to collect before calling

Veronica Di Polo has given the following guidance to inbound agents — these are the details they want you to collect from the user before you submit an inquiry. If you don't have an answer, ask the user in plain language first. Do not guess.

- Service type they offer (consulting, coaching, design, writing, etc.) and typical client value
- Current marketing bottleneck (leads coming too late, proposals stalling, content not converting, unclear messaging)
- Business stage and approximate annual revenue
- Geographic location or target client geography
- Whether they prefer ongoing work, short-term projects, or packaged solutions

## Tools

### `list_products` (tier T0)
List service offerings.

Call via MCP JSON-RPC:
```
POST https://clawviyo.com/c/veronica-di-polo/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "list_products", "arguments": { /* see mcp.json for schema */ } }
}
```

### `post_inquiry` (tier T2)
Submit a project inquiry.

Call via MCP JSON-RPC:
```
POST https://clawviyo.com/c/veronica-di-polo/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "post_inquiry", "arguments": { /* see mcp.json for schema */ } }
}
```

### `check_status` (tier T0)
Look up a prior inquiry.

Call via MCP JSON-RPC:
```
POST https://clawviyo.com/c/veronica-di-polo/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "check_status", "arguments": { /* see mcp.json for schema */ } }
}
```

## Tier model

| Tier | Required credentials |
|---|---|
| T0 | None (rate-limited by IP) |
| T1 | Resolvable AgentCard at your domain |
| T2 | T1 + OIDC-A delegation chain + verified, non-disposable human email |
| T3 | T2 + business-domain human email + agent reputation ≥ 50 |

If a call fails with `403 tier_not_met`, the response includes a `missing` array explaining what to add.

## Honeypot fields

Schemas may include fields marked `x-clawviyo: honeypot`. Never fill these in — they exist to catch spam agents. Honest agents simply ignore them.