Warm-intro assistants
Build agents that search the graph, explain the path, and request intros with real context instead of cold outbound.
Mutle exposes identity, search, feed, messaging, graph pathfinding, and introductions through one OAuth platform. Use it to power warm-intro assistants, talent search, private network products, and high-signal professional workflows.
OAuth scopes
10+
Core workflows
Search, feed, graph
Action surface
Posts, messages, intros
Mutle API
curl -X POST https://mutl.buzzchat.site/api/v1/network/path \
-H "Authorization: Bearer USER_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"targetUid": "usr_target_42"
}'
{
"data": {
"path": [
{ "uid": "usr_me", "displayName": "You" },
{ "uid": "usr_mutual", "displayName": "Mutual Connector" },
{ "uid": "usr_target_42", "displayName": "Target Person" }
],
"trustScores": ["high", "medium"],
"totalScore": 7
}
}Possible use cases
Build agents that search the graph, explain the path, and request intros with real context instead of cold outbound.
Find people by role, company, industry, and location, then rank candidates by social proximity and trusted reach.
Route partnership requests, investor outreach, and advisory intros through the right mutuals instead of guessing who knows whom.
Embed Mutle identity, messaging, and graph actions into your own member experience without rebuilding the trust layer from scratch.
How it fits together
Step 1
Register your app
Create a developer application, configure redirect URIs, and choose the scopes your product genuinely needs.
Step 2
Get a user token
Use OAuth 2.0 authorization-code flow for member actions and client-credentials only for machine-safe reads.
Step 3
Ship graph-native workflows
Search, inspect a path, create an intro, read the inbox, or publish member activity through one coherent contract.
Design principles
Developer routes reuse the same system behavior as Mutle itself, so partner apps do not get a weaker or parallel network model.
User-bound actions stay user-bound. Sensitive flows require the authorization-code path instead of unsafe app-only assumptions.
The surface is not just CRUD. Search, pathfinding, messaging, and introductions are exposed as product workflows.
Mutle works well for AI assistants that need identity, search, feed, and action endpoints tied to an accountable user context.
Scopes worth knowing
Mutle scopes map to real product actions. Some are self-serve, and some remain restricted because they move through the trust graph or message on behalf of a member.
Sign in with Mutle and fetch the member identity your integration is acting for.
Read the member's first-degree trusted network with clean, app-ready profile data.
Search across public profiles by name, role, company, industry, and location.
Read feed, posts, and notification surfaces tied to the authenticated member.
Create posts, comment on discussions, and drive real social actions through the same rules as the first-party product.
Read conversation state and send direct messages where the trust relationship already exists.
Calculate trusted routes between a member and a target node in the graph.
Create multi-hop intro requests with message quality, path integrity, and privacy rules enforced.
Start building
The public docs are live, the console is ready, and the API surface now includes search, feed, post actions, notifications, conversations, pathfinding, and introductions.
Great for concierge products, recruiting, founder outreach, and AI networking assistants.
Useful when your integration needs a living member activity surface, not just static profile data.
Best when you want continuity after a trusted handoff instead of exporting users into email chains.