# Using SpecJoin with an agent

Website: https://specjoin.com
REST base: https://specjoin.com/api/v1
OpenAPI: https://specjoin.com/api/openapi.json
MCP: https://specjoin.peanut20.chatgpt.site/mcp (Streamable HTTP POST; read-only evaluation; OpenAI OAuth)
Tool card: https://specjoin.com/.well-known/mcp/server-card.json
Human guide: https://specjoin.com/docs/agents

Workflow
1. Resolve the manufacturer's exact model/part number. Do not treat port variants as interchangeable or pick the first ambiguous result.
2. Reuse the returned SpecJoin ID. For accessory results, supply computer_id and category chargers, monitors or docks. Add accessory_id to check one pair. Follow next_offset for more pages.
3. Keep status, conditions, missing information, cables, software, supplies, operating system and sources together. Unknown means insufficient evidence, not that a product cannot work.
4. Match identities to your own SKU mapping and stock. SpecJoin provides neither prices nor availability.

Tools
search_products: q; optional kind, manufacturer, offset, limit (up to 20).
resolve_product: q; optional manufacturer. Returns exact/ambiguous identity.
get_product: product_id.
get_accessories: computer_id, category; optional accessory_id, offset, limit (up to 20).
check_dock: computer_id, dock_id. Screen and charging findings are independent; screen examples are not the full maximum.
structuredContent.data contains the same response as the corresponding REST endpoint. Errors retain HTTP status and Retry-After where available.

Example arguments
resolve_product: {"q":"Dell Latitude 5410","manufacturer":"Dell"}
check_dock: {"computer_id":"dell-latitude-5410-usbc","dock_id":"dell-wd19"}
get_accessories: {"computer_id":"lenovo-thinkpad-x250","category":"chargers","accessory_id":"lenovo-psu-0a36258"}

Equivalent REST requests
GET /resolve?q=Dell%20Latitude%205410&manufacturer=Dell
GET /dock/overview?host_id=dell-latitude-5410-usbc&dock_id=dell-wd19
GET /accessories/chargers?computer_id=lenovo-thinkpad-x250&charger_id=lenovo-psu-0a36258

Limits and access
Free evaluation, not guaranteed production service. Keep traffic below 120 requests/minute; temporary per-address protection applies. JSON bodies must be uncompressed and at most 32 KB. On rate limits, wait Retry-After. Cache reusable responses; use periodic downloads for larger agreed-scope imports.
Sites requires OpenAI OAuth sign-in for MCP connections. Use an OAuth-capable client. No account credentials belong in tool arguments. The REST evaluation API needs no sign-in. Paid access uses the REST API and a server-side SpecJoin key, not this evaluation MCP interface. Supplied keys are not silently treated as free access.
Send only product identities and hardware requirements. No customer information, orders, checkout actions, payments, account changes or private inventory uploads.

Coverage
Reviewed computers, docks, monitors, power supplies, cables and adapters. Connections, screens and charging only. No CPU/RAM/storage upgrade matching, full peripheral certification or physical testing. Versions and source review dates accompany applicable responses. Preserve unknowns when evidence needs review.