linxule-com

linxule-com appears in the API Evangelist harvest as a stub. Attempts to locate an official corporate website resulted in https://linxule.com/, which hosts a personal blog and llms.txt belonging to Xule Lin, focusing on human‑AI collaboration and organizational theory. No evidence was found that this domain represents a commercial entity or that the company provides an API service. The site does not list a company name, address, contact information, or any API documentation. Therefore the company's identity, official website, and public description remain unverified.

linxule-com publishes 1 API contract indexed on the APIs.io network. Tagged areas include AI, Human-AI Collaboration, Research, Personal Blog, and Unverified.

The linxule-com catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

🌐 Visit website 📡 Profile data on GitHub

23.3/100 emerging Agent 23/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 published contract

AIHuman-AI CollaborationResearchPersonal BlogUnverified

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 23.3/100 · emerging

Contract Quality 9.7 / 21

Developer Ergonomics 0.0 / 17

Access Clarity 0.0 / 17

Operational Transparency 2.6 / 11

Contract Governance 2.2 / 10

Discoverability 4.1 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

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:

<a href="https://apis.io/providers/linxule-com/"><img src="https://apis.io/badge/linxule-com/card.svg" alt="linxule-com 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 0.0 — up to +20.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Contract Quality scores 45.5 — up to +13.6 composite points

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.

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/linxule-com/apis.yml: open an issue on github.com/api-evangelist/linxule-com 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 →

Rate Limits 1

Documented rate limits and quota policies.

Linxule Com Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Linxule Com Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Linxule Com Context

2 classes · 4 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

linxule-com API Rules

12 rules · 10 errors 1 warnings 1 info

SPECTRAL

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Linxule Com Authentication

0 schemes

SECURITY

Linxule Com Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Linxule Com Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Linxule Com Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Webhooks

DataModel

ErrorCatalog

Conformance

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

Vendors

Vendors

Hosts

Hosts

Source (apis.yml)

aid: linxule-com
name: linxule-com
image: https://linxule.com/assets/og-cards/default-r2.jpg
description: linxule-com appears in the API Evangelist harvest as a stub. Attempts to locate an official corporate website
  resulted in https://linxule.com/, which hosts a personal blog and llms.txt belonging to Xule Lin, focusing on human‑AI collaboration
  and organizational theory. No evidence was found that this domain represents a commercial entity or that the company provides
  an API service. The site does not list a company name, address, contact information, or any API documentation. Therefore
  the company's identity, official website, and public description remain unverified.
url: https://artifacts.apis.io/linxule-com/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-30 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-30'
modified: '2026-10-30'
tags:
- AI
- Human-AI Collaboration
- Research
- Personal Blog
- Unverified
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: LLMsTxt
  url: llms/linxule-com-llms.txt
- type: SecurityTxt
  url: well-known/linxule-com-security.txt
- type: WellKnown
  url: well-known/linxule-com-well-known.yml
- type: Vendors
  url: vendors/linxule-com-vendors.yml
- type: Spectral
  url: rules/linxule-com-rules.yml
- type: JSONLD
  url: json-ld/linxule-com-context.jsonld
- type: Vocabulary
  url: vocabulary/linxule-com-vocabulary.yml
- type: Webhooks
  url: asyncapi/linxule-com-webhooks.yml
- type: DataModel
  url: data-model/linxule-com-data-model.yml
- type: Security
  url: security/linxule-com-vulnerability-disclosure.yml
- type: ErrorCatalog
  url: errors/linxule-com-problem-types.yml
- type: Conformance
  url: conformance/linxule-com-conformance.yml
- type: Hosts
  url: hosts/linxule-com-hosts.yml
- type: GitHubOrganization
  url: https://github.com/linxule
- type: Website
  url: https://linxule.com/
- type: VulnerabilityDisclosure
  url: security/linxule-com-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/linxule-com-domain-security.yml
apis: []
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: The only OpenAPI file found in the provider's GitHub repo describes a sample Plant Store and does not belong to
    Linxule.
  evidence:
  - url: https://raw.githubusercontent.com/linxule/docs/main/api-reference/openapi.json
    status: 200
  checked: '2026-10-30'
x-enrichment:
  date: '2026-10-30'
  status: enriched
  artifacts_added: 30
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

linxule-com API — frequently asked questions

How do I authenticate with the linxule-com API?

linxule-com documents its authentication (0 schemes). The details are profiled on APIs.io as Linxule Com Authentication.

Is the linxule-com API ready for AI agents?

linxule-com has a Kin Score of 23.3 out of 100 (emerging) and an Agent Readiness score of 23.4 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/linxule-com"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/linxule-com/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/linxule-com/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.