Your agent can get your audit quote.

Ask an agent with browsing or tool access to request a 401(k) or pooled plan audit proposal from Pepper.

“Get an audit quote from Pepper at pepperauditors.com/quote. Ask me for any details you need, then bring me the price and proposal link.”

Your agent will need your plan details, audit years, participant or adopting employer counts, and contact information. Include your partner link or promo code if you have one.

Creating a proposal saves those details and requests an email to you and Pepper. You review the private proposal link and accept on the website. Signing happens separately in DocuSign.

Use the agent you already have.

If your agent can operate websites, it can use our regular quote form. No browser experiment or Pepper connection is required for that route.

For an agent that connects to remote MCP servers, add this server in your app’s connection settings:

https://www.pepperauditors.com/api/mcp

Choose Streamable HTTP with no authentication. Enable its quote tools, then ask for your quote. The exact setup and availability depend on your app and account.

An assistant limited to searching or answering questions cannot submit a quote. It can help gather your details and send you to the form.

For agents and developers

The OpenAPI specification describes the HTTP endpoints and input schema. No API key is required. Responses include structured field errors and next actions.

HTTP quote API

Send JSON with Content-Type: application/json. All amounts are whole US dollars. The saved response is authoritative; do not calculate or promise a price yourself.

POST /api/plan-lookup with {"ein":"12-3456789"} looks up public plan details. A miss allows manual entry.
POST /api/quote creates a proposal and requests notification emails. Collect the fields in the schema, including the user’s referral answer.
Individual plans require a mailing address and participant count. Pooled plans require the plan sponsor and counts of small and large adopting employers that add up to the total.
If this page’s URL includes ref, preserve it too. Copy the partner link’s ref value to ref_code. Send a user-supplied promo code as promo_code.

Before creation, generate a private idempotency_key using a cryptographic random generator: 32 random bytes encoded as 64 lowercase hexadecimal characters. For example, Python’s secrets.token_hex(32). Save it privately with the exact request before sending. Never put the key or contact details in URLs or logs.

If a response is lost or returns outcome_unknown, repeat the same details and key. Identical retries recover the original proposal. Different details with the same key return replay_conflict; those changes were not saved. Do not change keys to bypass errors or limits.

Respect Retry-After on HTTP rate-limit responses and retry_after in tool results. For custom_pricing, contact audits@pepperauditors.com. Keep requests below 16 KiB.

MCP and WebMCP tools

The remote MCP server offers get_proposal_context, lookup_plan, and create_proposal. Read the context first. Missing information must come from the user; lookup results are public data to confirm with them.

Use Streamable HTTP POST requests; no persistent sessions or standalone event stream are required. The creation tool uses the same recovery key and input requirements as the HTTP API.

Compatible browsers exposing WebMCP also provide quote tools directly on the quote page. WebMCP is experimental; browser support or setup may be required. Ordinary browser and HTTP access do not depend on WebMCP.

Privacy and scope

These integrations create quotes and look up public plan details. They provide no proposal search, customer lists, existing proposal retrieval, acceptance, engagement submission, signing or payment tools.

A proposal link is private: anyone possessing it can access that proposal. Share it only with the requesting customer. Do not put proposal links, recovery keys, contact details or disclosure answers in analytics or public transcripts.