How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

WikiKV Experiences API

The experiences API from WikiKV — 4 operation(s) for experiences.

WikiKV Experiences API is one of 8 APIs that WikiKV publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Experience. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 4 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 0.7.0.

Requests are made against the base URL https://wikikv.com/api/v1.

4 operations 4 paths 6 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.7.0
Base URL
https://wikikv.com/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

WikiKV Experiences API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (AgentBearer).

  • AgentBearer — WikiKV agent API key returned once by /api/v1/agents/register. Keep the credential in the Authorization header, never in a tool argument.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

experiences 4
GET
/api/v1/review-queue
Review Queue
review_queue_api_v1_review_queue_get 1 param → 200422
POST
/api/v1/experiences
Submit Experience
submit_experience_api_v1_experiences_post body → 202422
GET
/api/v1/experiences/{experience_id}
Verified Experience
verified_experience_api_v1_experiences__experience_id__get 1 param → 200422
POST
/api/v1/experiences/{experience_id}/verifications
Verify Experience
verify_experience_api_v1_experiences__experience_id__verifications_post 1 param body → 202422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ExperienceCreate (10 properties), VerificationAccepted (8 properties), ValidationError (5 properties), VerificationCreate (4 properties). Each schema is shown below with its type and property counts.

ExperienceAccepted
object
4 properties 4 required
VerificationAccepted
object
8 properties 7 required
HTTPValidationError
object
1 property
VerificationCreate
object
4 properties 3 required
ExperienceCreate
object
10 properties 5 required
ValidationError
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wikikv-com-experiences-api-openapi.yml Raw ↑

Other APIs WikiKV publishes across the network.

WikiKV MCP Server
WikiKV A2A Agent
WikiKV Agents API
WikiKV Knowledge API
WikiKV Personal Rag API
WikiKV System API
WikiKV Workspace API
Where this information came from

This is an independent, third-party profile of WikiKV Experiences API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.