io.github.codyz123/schelling-protocol

NPM · @SCHELLING/MCP-SERVER · SCANNED AUG 3

Universal coordination protocol for AI agents. Discovery, matching, and negotiation.

Available components

+18 this week 64 64 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 147 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 4557 tokens (~99/item across 46 items; 46 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage96

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
89% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @schelling/mcp-server

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add codyz123-schelling-protocol -- npx -y @schelling/mcp-server

# add to Codex CLI

codex mcp add codyz123-schelling-protocol -- npx -y @schelling/mcp-server

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "codyz123-schelling-protocol": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@schelling/mcp-server"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add codyz123-schelling-protocol --command npx --arg -y --arg @schelling/mcp-server

# ~/.hermes/config.yaml

mcp_servers:
  codyz123-schelling-protocol:
    command: "npx"
    args: ["-y", "@schelling/mcp-server"]

// mcp.json

{
  "mcpServers": {
    "codyz123-schelling-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@schelling/mcp-server"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +43
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
1 Aug 26 +16
- Tool coverage: unverified → 100 ▲ functional
31 Jul 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 46

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@schelling/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 46 exposed · ~4,557 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

schelling.accept_delivery ~101

Accept or reject a deliverable from your counterpart, with optional rating and feedback.

Input Output Examples

Name	Type	Req	Description
accepted	boolean	yes	Accept (true) or reject (false)
delivery_id	string	yes	Delivery ID to respond to
feedback	string	—	Feedback on the deliverable
idempotency_key	string	—	—
rating	number	—	Quality rating 0-1
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.analytics ~64

System-wide analytics dashboard (admin only). Network statistics, cluster health, and growth metrics.

Input Output Examples

Name	Type	Req	Description
admin_token	string	yes	Admin authentication token
cluster_id	string	—	Filter by cluster
time_range	string	—	ISO 8601 date range

No output schema declared.

No examples provided.

schelling.cluster_info ~60

Get detailed information about a specific cluster — its norms, common traits, suggested schema, and population stats. Useful before registering.

Input Output Examples

Name	Type	Req	Description
cluster_id	string	yes	The cluster ID to inspect (e.g. 'hiring.engineering.frontend')

No output schema declared.

No examples provided.

schelling.clusters ~142

Browse the coordination network. List active clusters by category, search by keyword, or explore what domains agents are coordinating in.

Input Output Examples

Name	Type	Req	Description
action	string	—	Action: list (default), search, or describe a specific cluster
cursor	string	—	Pagination cursor from previous response
limit	number	—	Max results (default 50, max 200)
min_population	number	—	Minimum number of active participants
prefix	string	—	Filter by namespace prefix (e.g. 'hiring.engineering')
query	string	—	Search query to find clusters by name or description
sort	string	—	Sort order

No output schema declared.

No examples provided.

schelling.commit ~76

Commit to a candidate (INTERESTED to COMMITTED). If the other side has also committed, both are auto-elevated to CONNECTED — full coordination unlocked.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
idempotency_key	string	—	—
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.connections ~120

List your candidate pairs with their funnel stages and visible traits. See who you've discovered, expressed interest in, or connected with.

Input Output Examples

Name	Type	Req	Description
cluster_filter	string	—	Filter by cluster
cursor	string	—	—
limit	number	—	Max results
mode_filter	string	—	Filter by funnel mode
stage_filter	number	—	Minimum stage: 1=DISCOVERED, 2=INTERESTED, 3=COMMITTED, 4=CONNECTED
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.contract ~204

Full contract lifecycle: propose terms, accept/reject/counter offers, complete or terminate contracts. Supports multi-round negotiation with milestones.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Contract action
candidate_id	string	—	Candidate pair ID (for propose/list)
contract_id	string	—	Contract ID (for accept/reject/counter/complete/terminate)
dispute_content_disclosure	boolean	—	Allow contract content in disputes
expires_at	string	—	ISO 8601 expiration
idempotency_key	string	—	—
milestones	array	—	Milestone definitions
reason	string	—	Reason (for reject/terminate)
safe_types	array	—	Allowed deliverable types
status	string	—	Status filter (for list)
terms	—	—	Contract terms as JSON
terms_schema_version	string	—	—
type	string	—	Contract type
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.decline ~90

Decline a candidate. Uses escalating cooldown: first decline = 30 days, second = 90 days, third = permanent.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
feedback	—	—	Structured feedback to improve future matches
idempotency_key	string	—	—
reason	string	—	Reason for declining
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.delete_account ~53

Permanently delete your account and all associated data. This cannot be undone.

Input Output Examples

Name	Type	Req	Description
confirmation	string	yes	Must be exactly 'PERMANENTLY_DELETE'
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.deliver ~106

Deliver an artifact as fulfillment of a contract or milestone. Supports any content type.

Input Output Examples

Name	Type	Req	Description
contract_id	string	yes	Contract to deliver against
deliverable	—	—	Deliverable: {type, content, content_type?, filename?, metadata?, checksum?}
idempotency_key	string	—	—
message	string	—	Accompanying message
milestone_id	string	—	Specific milestone being fulfilled
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.deliveries ~57

List deliverables for a contract, optionally filtered by status.

Input Output Examples

Name	Type	Req	Description
contract_id	string	yes	Contract ID
status_filter	string	—	Filter by delivery status
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.describe ~45

Discover what the Schelling coordination network offers. Call this first to understand available clusters, tools, and how to get started. Returns a compact overview designed for AI agents.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schelling.direct ~85

Share direct contact info with a connected counterpart. Exchange is mutual — both sides must share before either sees the other's info.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
contact_info	string	yes	Your contact info (email, phone, URL, etc.)
idempotency_key	string	—	—
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.dispute ~120

File a formal dispute against a counterpart. Triggers the agent jury system for resolution. Requires CONNECTED stage.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
delivery_claims	array	—	Claims about failed deliverables
evidence	array	—	Evidence URLs or references
idempotency_key	string	—	—
reason	string	yes	Reason for dispute (max 5000 chars)
trait_claims	array	—	Claims about misrepresented traits
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.event ~183

Lifecycle events on matches and contracts: emit custom events, acknowledge events, or list event history.

Input Output Examples

Name	Type	Req	Description
ack_deadline_hours	number	—	Hours until ack deadline
action	string	yes	Action to perform
candidate_id	string	—	Candidate pair ID
contract_id	string	—	Contract ID
event_id	string	—	Event ID (for ack action)
event_type	string	—	Event type (e.g. milestone_reached, schedule_change)
idempotency_key	string	—	—
limit	number	—	Max events to return
payload	—	—	Event payload
requires_ack	boolean	—	Whether counterpart must acknowledge
response	string	—	Acknowledgment response
since	string	—	ISO 8601 timestamp filter
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.export ~49

Export all your data from the network (GDPR/CCPA compliance).

Input Output Examples

Name	Type	Req	Description
format	string	—	Export format (default: json)
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.inquire ~172

Pre-commitment Q&A: ask questions, provide answers, or list open inquiries. Available at INTERESTED stage before committing.

Input Output Examples

Name	Type	Req	Description
action	string	yes	ask a question, answer one, or list all
answer	string	—	Answer text (for answer action)
candidate_id	string	yes	Candidate pair ID
category	string	—	Question category
confidence	number	—	Answer confidence 0-1
idempotency_key	string	—	—
inquiry_id	string	—	Inquiry ID (for answer action)
question	string	—	Question text (for ask action)
required	boolean	—	Whether an answer is required before committing
source	string	—	Answer source
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.interest ~86

Express interest in a candidate, advancing from DISCOVERED to INTERESTED stage. This signals you want to explore this match further.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID from search results
contract_proposal	—	—	Contract proposal (for auction mode)
idempotency_key	string	—	—
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.jury_duty ~42

Check if you've been assigned as a juror for any disputes. Community-driven dispute resolution.

Input Output Examples

Name	Type	Req	Description
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.jury_verdict ~83

Submit your verdict on a dispute as a juror.

Input Output Examples

Name	Type	Req	Description
dispute_id	string	yes	Dispute ID
idempotency_key	string	—	—
reasoning	string	yes	Reasoning for your verdict (max 5000 chars)
user_token	string	yes	Your bearer token
verdict	string	yes	Your verdict

No output schema declared.

No examples provided.

schelling.list_tools ~96

Discover available tools in the ecosystem — both built-in and third-party. Tools enhance matching, verification, and coordination.

Input Output Examples

Name	Type	Req	Description
cluster_id	string	—	Filter by cluster relevance
cursor	string	—	—
limit	number	—	Max results
min_reputation	number	—	Minimum tool reputation score
query	string	—	Search tools by keyword
type	string	—	Tool type filter

No output schema declared.

No examples provided.

schelling.message ~73

Send a message through the relay to a connected counterpart. Requires CONNECTED stage.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
content	string	yes	Message content (max 5000 characters)
idempotency_key	string	—	—
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.messages ~77

Retrieve message history with a counterpart.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
cursor	string	—	—
limit	number	—	Max messages (default 50)
since	string	—	ISO 8601 timestamp — only messages after this time
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.my_insights ~44

Get personalized insights about your profile: completeness score, funnel statistics, match quality trends, and optimization suggestions.

Input Output Examples

Name	Type	Req	Description
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.notifications ~63

Check notifications from your push-based discovery subscriptions.

Input Output Examples

Name	Type	Req	Description
limit	number	—	Max notifications
since	string	—	ISO 8601 timestamp filter
subscription_id	string	—	Filter by subscription
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.onboard ~98

Start using Schelling with zero configuration. Describe what you need in plain English and get back a registration template with suggested cluster, traits, and preferences. The easiest way to get started.

Input Output Examples

Name	Type	Req	Description
cluster_id	string	—	Target cluster (auto-detected from your description if omitted)
natural_language	string	yes	What you want in plain English (e.g. 'I need a React developer in Denver, $120/hr')

No output schema declared.

No examples provided.

schelling.pending ~42

Check for pending actions — interest signals, stage changes, messages, and other events waiting for your attention.

Input Output Examples

Name	Type	Req	Description
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.quick_match ~87

Submit both sides of a coordination problem for instant matching. Provide a seeker and offerer profile and get an immediate compatibility assessment.

Input Output Examples

Name	Type	Req	Description
auto_connect	boolean	—	Auto-connect if match quality is high
offer	—	—	Offerer profile: {intent, traits?, cluster_id?}
seek	—	—	Seeker profile: {intent, traits?, preferences?, cluster_id?}

No output schema declared.

No examples provided.

schelling.quick_offer ~167

Advertise a service or capability in one call. Describe what you offer and get matched with seekers. Auto-registers and optionally subscribes to incoming requests.

Input Output Examples

Name	Type	Req	Description
auto_subscribe	boolean	—	Auto-subscribe to matching seekers (default true)
available_until	string	—	ISO 8601 availability deadline
cluster_id	string	—	Target cluster (auto-detected if omitted)
intent	string	yes	What you're offering in plain English (e.g. 'I do React development, 5 years experience, Denver, $90/hr')
notification_threshold	number	—	Minimum fit score for notifications (0-1)
traits	—	—	Structured traits for your offering
user_token	string	—	Bearer token (auto-registers if omitted)

No output schema declared.

No examples provided.

schelling.quick_seek ~188

Find what you need in one call. Describe your requirements in natural language or structured format. Auto-registers you if needed and returns ranked candidates immediately. The fastest way to search.

Input Output Examples

Name	Type	Req	Description
auto_advance	boolean	—	Auto-advance top candidates to INTERESTED stage
budget	—	—	Budget constraints: {min?, max?, currency?}
cluster_id	string	—	Target cluster (auto-detected if omitted)
constraints	—	—	Structured constraints as preference objects
deadline	string	—	ISO 8601 deadline for urgency
intent	string	yes	What you're looking for in plain English (e.g. 'Python developer, 5+ years, remote, under $100/hr')
max_results	number	—	Max candidates to return (default 5)
user_token	string	—	Bearer token (auto-registers you if omitted)

No output schema declared.

No examples provided.

schelling.reconsider ~55

Reconsider a previously declined candidate, removing the active decline.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
idempotency_key	string	—	—
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.refresh ~46

Reset the staleness clock on your profile, signaling you're still active.

Input Output Examples

Name	Type	Req	Description
idempotency_key	string	—	—
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.register ~310

Register a participant in the coordination network with structured traits and preferences. Use schelling.onboard first to get a template, then pass it here.

Input Output Examples

Name	Type	Req	Description
agent_capabilities	array	—	Agent capabilities
agent_model	string	—	AI model identifier
cluster_id	string	yes	Cluster to register in (e.g. 'hiring.engineering.frontend')
funnel_mode	string	—	Coordination mode (default: bilateral)
group_size	number	—	Target group size for group mode (2-50)
idempotency_key	string	—	Idempotency key to prevent duplicates
identity	—	—	Identity info: {name?, contact?, phone_hash?}
intent_embedding	array	—	16-dimensional intent vector
intents	array	—	Natural language intent descriptions (max 5)
media_refs	array	—	URLs to photos/media
phone_hash	string	—	SHA-256 hash of phone for Sybil resistance
preferences	array	—	Array of preference objects: [{trait_key, operator, value, weight}]
protocol_version	string	yes	Must be '3.0'
role	string	—	Role within the cluster (cluster-defined)
text_profile	—	—	Free text: {description?, seeking?, interests?, values_text?}
traits	array	—	Array of trait objects: [{key, value, value_type, visibility}]
user_token	string	—	Existing token for re-registration

No output schema declared.

No examples provided.

schelling.register_tool ~191

Register a third-party tool in the Schelling ecosystem. Tools extend coordination capabilities — skill assessments, background checks, portfolio reviews, and more.

Input Output Examples

Name	Type	Req	Description
cluster_scope	array	—	Clusters this tool applies to
description	string	yes	Full description
display_name	string	yes	Human-readable name
endpoint	string	yes	HTTPS endpoint for tool invocation
health_check_endpoint	string	—	—
idempotency_key	string	—	—
input_schema	—	—	JSON Schema for tool input
one_line_description	string	yes	One-line summary
output_schema	—	—	JSON Schema for tool output
pricing	—	—	Pricing: {model, amount?, currency?}
tool_id	string	yes	Namespaced tool ID: {developer}.{tool_name}
user_token	string	yes	Developer bearer token
version	string	yes	Semantic version

No output schema declared.

No examples provided.

schelling.relay_block ~58

Block or unblock message relay from a specific counterpart.

Input Output Examples

Name	Type	Req	Description
blocked	boolean	yes	true to block, false to unblock
candidate_id	string	yes	Candidate pair ID
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.report ~84

Report the outcome of a connection — positive, neutral, or negative. This feeds the learned ranking model and reputation system.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
feedback	—	—	Structured feedback
idempotency_key	string	—	—
outcome	string	yes	How the coordination went
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.reputation ~62

Check reputation scores — your own or a counterpart's. Shows trust level, interaction history, and cross-cluster reputation.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	—	Candidate pair ID to check counterpart's reputation
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.search ~178

Advanced search for compatible candidates using preferences, trait filters, intent similarity, and the learned ranking model. Supports natural language queries alongside structured filters.

Input Output Examples

Name	Type	Req	Description
capability_filters	array	—	Required agent capabilities
cluster_id	string	—	Cluster to search (defaults to your cluster)
cursor	string	—	Pagination cursor
idempotency_key	string	—	—
max_results	number	—	Max results (default 20)
min_advisory_score	number	—	Minimum match score threshold (0-1)
mode_filter	string	—	Filter by coordination mode
natural_language	string	—	Natural language search query
preference_overrides	array	—	Temporary preference overrides for this search
trait_filters	array	—	Hard trait filters
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.server_info ~27

Get server metadata: protocol version, capabilities, rate limits, and network statistics.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schelling.subscribe ~165

Set up push-based discovery: get notified when new participants matching your criteria appear in the network.

Input Output Examples

Name	Type	Req	Description
action	string	—	Create a subscription or list existing ones
capability_filters	array	—	Required capabilities
cluster_filter	string	—	Cluster to watch
idempotency_key	string	—	—
intent_embedding	array	—	16-dim intent vector for similarity matching
max_notifications_per_day	number	—	Daily notification cap
mode_filter	string	—	Funnel mode filter
threshold	number	—	Minimum match score for notification (0-1)
trait_filters	array	—	Trait-based filters
ttl_days	number	—	Subscription lifetime in days
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.tool_feedback ~72

Rate a tool invocation — helps the ecosystem surface the best tools.

Input Output Examples

Name	Type	Req	Description
comment	string	—	Optional feedback
invocation_id	string	—	—
rating	string	yes	Your rating
tool_id	string	yes	Tool to rate
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.tool_invoke ~56

Invoke a tool from the ecosystem (built-in or third-party).

Input Output Examples

Name	Type	Req	Description
input	—	—	Tool-specific input payload
tool_id	string	yes	Tool to invoke
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.unsubscribe ~39

Cancel a push-based discovery subscription.

Input Output Examples

Name	Type	Req	Description
subscription_id	string	yes	Subscription to cancel
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.update ~148

Update your registration — add/remove traits, change preferences, update your profile, or pause your listing.

Input Output Examples

Name	Type	Req	Description
idempotency_key	string	—	—
intent_embedding	array	—	Updated 16-dim intent vector
intents	array	—	Updated intent descriptions
preferences	array	—	Preferences to upsert
remove_preferences	array	—	Preference trait_keys to remove
remove_traits	array	—	Trait keys to remove
status	string	—	Set status (paused hides from search)
text_profile	—	—	Updated text profile
traits	array	—	Traits to upsert
user_token	string	yes	Your bearer token from registration

No output schema declared.

No examples provided.

schelling.verify ~124

Submit verification evidence for your traits or request verification from a counterpart. Verified traits build trust.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Submit your own evidence or request from counterpart
candidate_id	string	—	Candidate pair ID (for request action)
evidence_data	string	—	Evidence payload
evidence_type	string	—	Type of evidence
idempotency_key	string	—	—
requested_tier	string	—	Requested verification level
trait_key	string	yes	Trait key to verify
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

schelling.withdraw ~69

Withdraw from a COMMITTED or CONNECTED match, resetting to INTERESTED stage.

Input Output Examples

Name	Type	Req	Description
candidate_id	string	yes	Candidate pair ID
idempotency_key	string	—	—
reason	string	—	Reason for withdrawal
user_token	string	yes	Your bearer token

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug