Wikidocs
Wikidocs was a real-time collaboration startup (wikidocs.io) that built a framework for turning any web page into a live, editable, multi-user "docs" service — enabling real-time content creation, editing, and sharing directly in the browser without waiting for updated versions. Backed by Speedinvest, the company was acquired by Atlassian in September 2014 and its collaboration technology was folded into Atlassian's products. Wikidocs no longer operates as an independent product: its former domain, wikidocs.io, is now a parked and email-forwarded registrar domain with no live developer portal, API, documentation, or machine-readable surface to enrich.
Wikidocs is profiled on the APIs.io network. Tagged areas include Company, Collaboration, Real-Time, Documentation, and Productivity.
2.6/100
minimal
▬ flat
Agent
0/100
human only
0 APIs
Kin Score
Kin Score
How this is scored →scored 2026-11-13 · rubric v0.28.0
Composite quality — 2.6/100 · minimal
Agent readiness — 0/100 · human only
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/wikidocs/"><img src="https://apis.io/badge/wikidocs/card.svg" alt="Wikidocs on APIs.io — Kin Score by API Evangelist"></a>Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
- Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
- MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
- Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
- Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
- Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
- Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
13 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
- Contract Quality scores 0.0 — up to +25.0 composite points Ask about this →
- Developer Ergonomics scores 0.0 — up to +20.0 composite points Ask about this →
- Access Clarity scores 0.0 — up to +20.0 composite points Ask about this →
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/wikidocs/apis.yml: open an issue on github.com/api-evangelist/wikidocs to ask a question or point us at an artifact you publish.
Submit an artifact on GitHub — free →
Manage your own listing — the Influence plan, $499/mo →
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.