Skip to content

Wikshi / Documentation

Bring your agent.
We’ll bring the tools.

A practical guide to giving your agent contacts, email, voice, and video through x402 on Hedera.

Try now for free

01 / Get started

Tell your agent what you need.

Start with a mission, an approved budget, and the people your agent is allowed to contact. Wikshi supplies the capabilities. Your agent owns the plan.

Find the right people for my brief, prepare an introduction, and recommend whether email, a phone call, or a short video meeting is the best next step.

Read the workflow skill ↗ or choose your agent ↗.

02 / Capabilities

Choose the right channel.

Discovery
Search for people and companies. Enrich available business contact details. Metered by search or lookup.
Email
An agent-owned address and inbox for sending, receiving, and following up. Metered by email usage.
Phone
Mission-led voice calls with a duration limit, status, and original transcript. Metered by call duration.
Video
Guest-facing Wikshi meeting links for live conversations. Metered by session duration.
Explore each service ↗

03 / Video meetings

A meeting with a mission.

Your agent arranges a time with the guest, supplies the questions, and sets a time limit of up to three minutes.

  1. Pay and receive the link

    The paid operation returns a guest-facing meeting URL and a separate private retrieval credential. Share only the guest link.

  2. Have the conversation

    The guest opens a Wikshi video call in their browser. Your agent asks the questions and gathers the information. Scheduling and invitations belong to your agent; this flow does not join external Zoom or Teams rooms.

  3. Retrieve the transcript

    Check session status with the private credential. Once completed, retrieve the original transcript without a second payment. Keep the transcript unchanged when presenting it as a verbatim record.

Session states

Not started, in progress, processing, and completed distinguish the normal lifecycle. Failed and expired sessions remain explicit so the agent does not mistake missing data for a completed call.

One-use links and private access

A purchase is for one conversation. Close the guest session after completion while retaining authorized access to its stored transcript. A public transaction receipt is never sufficient authorization to read private conversations.

04 / x402 on Hedera

Know the cost before the call.

Pay in USDC without a credit card or signup. The service quote defines the price, billing unit, maximum spend, and expiry.

  1. Quote and authorize

    The agent reviews the service requirements and pays the quoted ceiling through the supported x402 flow.

  2. Execute within the budget

    A verified payment is bound to one operation. Duration caps constrain calls and video conversations.

  3. Measure and reconcile

    Compute the charge from measured units and the agreed rounding rules. Return unused prepaid balance in a separate Hedera refund.

  4. Return the result

    Link the payment, usage, and refund status in the receipt. Use a private credential for session results.

This is a prepayment-and-refund flow, not native upto authorization or continuous on-chain streaming. The calculator explains the arithmetic; the service quote determines the actual rate.

Explore metering ↗

05 / Responsible use

Useful access. Clear boundaries.

Only contact people within the user’s authority and applicable consent requirements. Ask for confirmation before sending messages or placing calls unless that scope has already been explicitly delegated. Respect opt-outs and spending limits.

Keep private messages, contacts, and transcripts off-chain. Scope each inbox and retrieval credential to its owner. Never place private credentials into public meeting invitations or payment receipts.

Retries should refer to the same operation rather than placing another call or sending a duplicate email. Preserve webhook verification, idempotency, and explicit error states in any integration.