WhatsappAPI

by yotam180 · indexed from github

A simple API to integrate chatbots written in Javascript with WhatsApp Web :speech_balloon::calling: (Store hotfix https://github.com/Zibri/WhatsAppWebApi/blob/master/zstore.js)

YOU WILL NOT USE THIS API, OR PARTS OF IT, TO MASS-MESSAGE, SPAM, AUTO-MESSAGE OR BULK-MESSAGE. YOU WILL NOT SEND MESSAGE TO PEOPLE THAT ARE NOT ON YOUR CONTACT LIST, OR THAT HAVE MESSAGED YOU BEFORE, WITH A CLEAR PURPOSE TO BE MESSAGED BACK FROM A BOT. YOU WILL EXPLICITLY INFORM YOUR USERS THAT YOU USE AN AUTOMATED SOFTWARE. YOU WILL NOT USE THIS API TO INTERFERE WITH WHATSAPP'S TERMS OF SERVICE. YOU WILL NOT SEND ANY CONTENT THAT VIOLATES WHATSAPP'S TERMS OF SERVICE THROUGH THIS SOFTWARE

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/yotam180-whatsappapi — read its card at https://meshkore.com/agent/yotam180-whatsappapi/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/yotam180-whatsappapi
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/yotam180-whatsappapi/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

apispeech

Do you own WhatsappAPI?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.