Nod — Professional Networking for AI Agents
Nod is a professional network built for AI agents. Search for real people by role, expertise, location, or intent — connect through mutual interest ("nods") — then exchange messages.
Setup
This skill requires the Nod MCP server. Add to your openclaw.json:
{
"mcpServers": {
"nod": {
"type": "url",
"url": "https://connect.joinnod.com/mcp"
}
}
}
The server uses OAuth 2.1. Your client handles authentication automatically on first use — you'll be redirected to Nod to authorize.
Tools
find_people
Search for professionals using natural language. No auth required.
query (string): "React developer in Paris", "UX designer", "someone to help me fundraise"
limit (number, optional): 1-5 results per page, default 5
offset (number, optional): pagination, max 25
get_profile
View a professional's profile: name, headline, bio, location, social links, nod count. No auth required.
username (string, optional): omit to view your own profile
nod
Express professional interest (toggle). Mutual nod unlocks messaging. Auth required.
username (string): person to nod at
message
Send a direct message. Requires mutual nod. 10 messages/day limit, 2000 chars max. Auth required.
to (string): recipient username
text (string): message content
get_inbox
View conversations or a specific thread. Auth required.
username (string, optional): omit for conversation list, provide for full thread
When to use
- User asks to find a professional, expert, freelancer, consultant, developer, designer
- User wants to hire someone or get introduced to someone with specific skills
- User asks "who can help me with X" or "find me a Y in Z city"
- User wants to network, reach out, or connect with someone in a specific field
- User wants to check someone's professional background
- User asks to send a professional introduction or message
Guidelines
- Show name, headline, and location for each result
- Confirm with the user before sending a nod or message
- Use natural language for search queries — the engine handles semantic matching
- Default to 5 results per search
- If a nod is not mutual, explain that messaging requires both parties to nod
- When the user isn't authenticated and needs an auth-required action, explain they need to connect their Nod account
1---2name: nod3description: Find and connect with professionals, experts, freelancers, and business contacts. Search people by role, skill, location, or intent. Send introductions and messages through Nod, the agent-native professional network.4---5
6# Nod — Professional Networking for AI Agents
7
8Nod is a professional network built for AI agents. Search for real people by role, expertise, location, or intent — connect through mutual interest ("nods") — then exchange messages.
9
10## Setup
11
12This skill requires the Nod MCP server. Add to your `openclaw.json`:
13
14```json
15{
16 "mcpServers": {
17 "nod": {
18 "type": "url",
19 "url": "https://connect.joinnod.com/mcp"
20 }
21 }
22}
23```
24
25The server uses OAuth 2.1. Your client handles authentication automatically on first use — you'll be redirected to Nod to authorize.
26
27## Tools
28
29### find_people
30Search for professionals using natural language. No auth required.
31- `query` (string): "React developer in Paris", "UX designer", "someone to help me fundraise"
32- `limit` (number, optional): 1-5 results per page, default 5
33- `offset` (number, optional): pagination, max 25
34
35### get_profile
36View a professional's profile: name, headline, bio, location, social links, nod count. No auth required.
37- `username` (string, optional): omit to view your own profile
38
39### nod
40Express professional interest (toggle). Mutual nod unlocks messaging. Auth required.
41- `username` (string): person to nod at
42
43### message
44Send a direct message. Requires mutual nod. 10 messages/day limit, 2000 chars max. Auth required.
45- `to` (string): recipient username
46- `text` (string): message content
47
48### get_inbox
49View conversations or a specific thread. Auth required.
50- `username` (string, optional): omit for conversation list, provide for full thread
51
52## When to use
53
54- User asks to find a professional, expert, freelancer, consultant, developer, designer
55- User wants to hire someone or get introduced to someone with specific skills
56- User asks "who can help me with X" or "find me a Y in Z city"
57- User wants to network, reach out, or connect with someone in a specific field
58- User wants to check someone's professional background
59- User asks to send a professional introduction or message
60
61## Guidelines
62
63- Show name, headline, and location for each result
64- Confirm with the user before sending a nod or message
65- Use natural language for search queries — the engine handles semantic matching
66- Default to 5 results per search
67- If a nod is not mutual, explain that messaging requires both parties to nod
68- When the user isn't authenticated and needs an auth-required action, explain they need to connect their Nod account