78trust / 100

Email Send

by win.oneshotagent.com in Email & messaging

x402 APIPassing, checked 2 min ago

Send email with provisioned domain

POST
https://win.oneshotagent.com/v1/tools/email/send
Price
$0.001
per call in USDC
Uptime
100%
last 30 days
Response time
215 ms
292 ms slowest 5%
Last check
Passed
2 min ago, next in 27 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://win.oneshotagent.com/v1/tools/email/send

Each call costs $0.001 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://win.oneshotagent.com/v1/tools/email/send
content-type: application/json

{
  "body": "Email body content",
  "subject": "Hello from OneShot",
  "to": "[email protected]"
}

Parameters

ParameterTypeRequiredDescription
bodystringYes
subjectstringYes
tostring (email)Yes

Example response

The provider's example. We can't check it without paying.

{
  "receipt_id": "rcpt_uuid",
  "request_id": "uuid",
  "status": "processing",
  "tool": "email"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.001.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://win.oneshotagent.com/v1/tools/email/send' \
  -H 'content-type: application/json' \
  --data-raw '{"body":"Email body content","subject":"Hello from OneShot","to":"[email protected]"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://win.oneshotagent.com/v1/tools/email/send' \
  -H 'content-type: application/json' \
  --data-raw '{"body":"Email body content","subject":"Hello from OneShot","to":"[email protected]"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwin.oneshotagent.com%2Fv1%2Ftools%2Femail%2Fsend&method=POST
const res = await pay("https://win.oneshotagent.com/v1/tools/email/send", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "body": "Email body content",
    "subject": "Hello from OneShot",
    "to": "[email protected]"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://win.oneshotagent.com/v1/tools/email/send",
        json={
            "body": "Email body content",
            "subject": "Hello from OneShot",
            "to": "[email protected]",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 min agoPassed402173 ms$0.001
3 h agoPassed402252 ms$0.001
6 h agoPassed402208 ms$0.001
9 h agoPassed402209 ms$0.001
14 h agoPassed402222 ms$0.001
Show 10 older checks
19 h agoPassed402211 ms$0.001
24 h agoPassed402220 ms$0.001
30 h agoPassed402176 ms$0.001
35 h agoPassed402215 ms$0.001
40 h agoPassed402230 ms$0.001
45 h agoPassed402217 ms$0.001
2 days agoPassed402185 ms$0.001
2 days agoPassed402206 ms$0.001
3 days agoPassed402213 ms$0.001
3 days agoPassed402215 ms$0.001