| slack.url4.ai | Install Spec url4.ai |
Slack as a url4 sourceWhen an AI fetches a url4, some sources are websites. Others are people. slack.url4.ai turns a Slack workspace into a url4 active source. The AI sends a prompt, a real person sees it in Slack, and their reply comes back as the response. No API, no code, no training. Just a human answering a question in English. Setup (30 seconds) 1. Start the server locally. It detects your Slack desktop app automatically. |
$ curl localhost:5000/detect
{"found": true, "teams": [{"id": "T12345", "name": "My Workspace", "domain": "mycompany"}]}
$ curl -X POST localhost:5000/connect -H 'Content-Type: application/json' \
-d '{"team_id": "T12345", "domain": "mycompany"}'
{"ok": true, "key": "abc123def456", "team_name": "My Workspace", "prefix": "http://localhost:5000/v1/abc123def456/"}
|
|
No Slack app creation. No OAuth. It reads your existing Slack session from the desktop app. 2. Use it as a source in any url4: |
url4.ai/v1/?q=localhost:5000/v1/your-key/general!your+question&wait=5m url4.ai/v1/?q=localhost:5000/v1/your-key/@alice!are+you+free+friday&wait=1h url4.ai/v1/?q=0.5*localhost:5000/v1/your-key/movies~0.1|0.5*imdb.com!recommend+a+movie |
|
3. The prompt gets posted to the channel (or DM'd to the person). People reply in the thread. Their replies come back as the source response. What this is for Most url4 sources are services — databases, APIs, websites. But sometimes the best source is a person. Maybe there's no API for what you need. Maybe the answer requires judgment, taste, or lived experience. Maybe you just want to ask your friends. This is the human fallback. When no service exists, ask a person. URL format
Endpoints
Built by OpenMined. Read the url4 spec. |