Nichify Developer Resources

Everything you need to build on Nichify - the Vinted niche finder. API docs, MCP server, agent instructions, and PATs. If you are an AI agent (Claude, ChatGPT, Gemini), start with /agent-instructions.md.

Quick links

MCP server

Streamable HTTP at /mcp, spec 2025-06-18. Manifest at /mcp/manifest. Bearer nch_... auth.

Open manifest ->

MCP server card

Static discovery card at /.well-known/mcp.json. Points at transports, tools, and ui://nichify/... MCP Apps resources.

Open server card ->

OpenAPI 3.1 spec

Authoritative machine-readable spec with camelCase operationIds and structured errors (problem+json).

Open spec ->

Agent instructions

When-to-use / when-not-to-use rules for AI agents. Explicit dos and don'ts.

Read instructions ->

Personal Access Tokens

Create, list, and revoke PATs scoped to read or write.

Manage PATs ->

Agent auth guide

Step-by-step: how AI agents authenticate. Scopes, rotation, rate limits, Claude Desktop config snippet.

Read guide ->

Product context (llms.txt)

Short and full product context for agents, with FR / EN / DE / NL via Accept-Language.

Read llms.txt ->

Integration roadmap

Submission status on ChatGPT, Claude Desktop, and Gemini MCP registries.

View roadmap ->

Status page

Live liveness and build metadata. JSON at /api/status.

Open status ->

Hello world over MCP

With a PAT from /account/keys, list the tools Nichify exposes:

curl -X POST https://nichify.app/mcp \
  -H "Authorization: Bearer nch_your_token_here" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Then run whoami to confirm your identity and scopes:

curl -X POST https://nichify.app/mcp \
  -H "Authorization: Bearer nch_your_token_here" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"whoami","arguments":{}}}'

Hello world over REST

curl https://nichify.app/api/status
curl -H "Authorization: Bearer nch_your_token_here" https://nichify.app/api/analyses

Every error response is JSON with Content-Type: application/problem+json. Branch on error.code, not error.message.

Deeper context