@imqueue

@imqueue provides RPC over a message queue for service‑oriented Node.js and TypeScript back‑ends. Its self‑describing services generate typed clients automatically, eliminating boilerplate. The platform enables developers to talk to services as if they were local functions, leveraging a message‑queue transport layer for scalable, decoupled architectures.

@imqueue is listed with 2 APIs on the APIs.io network. Tagged areas include Messaging, TypeScript, Node.js, RPC, and Queues.

The @imqueue catalog on APIs.io includes 1 Spectral governance ruleset.

@imqueue’s developer surface includes CLI, support, getting-started guide, documentation, engineering blog, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

31.4/100 thin Agent 16/100 agent aware Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

2 APIs

Messaging TypeScript Node.js RPC Queues

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 31.4/100 · thin

Contract Quality 2.0 / 21

Developer Ergonomics 7.3 / 17

Access Clarity 2.9 / 17

Operational Transparency 5.3 / 11

Contract Governance 2.2 / 10

Discoverability 5.8 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 16/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 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 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

MCP Tool Quality 6 / 6

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/imqueue-org/"><img src="https://apis.io/badge/imqueue-org/card.svg" alt="@imqueue 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 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 →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →

11 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 9.4 — up to +22.7 composite points Ask about this →
Access Clarity scores 17.0 — up to +16.6 composite points Ask about this →
Developer Ergonomics scores 42.9 — up to +11.4 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/imqueue-org/apis.yml: open an issue on github.com/api-evangelist/imqueue-org 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 →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Imqueue API

API reference for @imqueue services

@imqueue API

@imqueue API as documented publicly: 1 operations. Contract generated from the documentation by API Evangelist (2026-11-12); not the provider's own document.

@imqueue API pricing

Rate limits

maxRequests: maxRequests: 100
banLimit: banLimit: 250

Rate-limit details →

Rate Limits 1

Documented rate limits and quota policies.

@imqueue Rate Limits

2 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

@imqueue API Rules

20 rules · 18 error-severity 1 warn-severity 1 info-severity

SPECTRAL

Security Posture 2

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

@imqueue Domain Security

TLSv1.3

SECURITY

@imqueue Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Spectral

Spectral

Vocabulary

Vocabulary

Conformance

Conformance

Build 4

SDKs, sample code, and the tooling you integrate with

CLI

CLI

SDKs

SDKs

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 5

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

SecurityTxt

SecurityTxt

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: imqueue-org
name: '@imqueue'
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: unreadable
  source:
  - rate-limits
  - security
  generated: '2026-11-13'
  method: derived
image: https://imqueue.org/images/og-org.png
description: '@imqueue provides RPC over a message queue for service‑oriented Node.js and TypeScript back‑ends. Its self‑describing
  services generate typed clients automatically, eliminating boilerplate. The platform enables developers to talk to services
  as if they were local functions, leveraging a message‑queue transport layer for scalable, decoupled architectures.'
url: https://artifacts.apis.io/imqueue-org/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-12 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-12'
modified: '2026-11-12'
tags:
- Messaging
- TypeScript
- Node.js
- RPC
- Queues
tags_raw:
- Messaging
- TypeScript
- Node.js
- RPC
- Queue
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: RateLimits
  url: rate-limits/imqueue-org-rate-limits.yml
- type: Spectral
  url: rules/imqueue-org-rules.yml
- type: Vocabulary
  url: vocabulary/imqueue-org-vocabulary.yml
- type: CLI
  url: cli/imqueue-org-cli.yml
- type: Conformance
  url: conformance/imqueue-org-conformance.yml
- type: LLMsTxt
  url: llms/imqueue-org-llms.txt
- type: SecurityTxt
  url: well-known/imqueue-org-security.txt
- type: SecurityTxt
  url: well-known/imqueue-org-imqueue-security.txt
- type: WellKnown
  url: well-known/imqueue-org-well-known.yml
- type: Hosts
  url: hosts/imqueue-org-hosts.yml
- type: Vendors
  url: vendors/imqueue-org-vendors.yml
- type: SDKs
  url: packages/imqueue-org-packages.yml
- type: Packages
  url: packages/imqueue-org-packages.yml
- type: TermsOfService
  url: https://imqueue.org/terms/
- type: Support
  url: https://imqueue.org/support/
- type: StatusPage
  url: https://imqueue.org/status/
- type: Security
  url: https://imqueue.org/mcp/security/
- type: PrivacyPolicy
  url: https://imqueue.org/privacy/
- type: GitHubOrganization
  url: https://github.com/imqueue
- type: GettingStarted
  url: https://imqueue.org/get-started/
- type: Documentation
  url: https://imqueue.org/docs/
- type: Blog
  url: https://imqueue.org/blog/
- type: VulnerabilityDisclosure
  url: security/imqueue-org-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/imqueue-org-domain-security.yml
- type: Website
  url: https://imqueue.org/
apis:
- name: Imqueue API
  description: API reference for @imqueue services
  humanURL: https://imqueue.org/api/
  aid: imqueue-org:imqueue-api
- aid: imqueue-org:imqueue-org-api
  name: '@imqueue API'
  description: '@imqueue API as documented publicly: 1 operations. Contract generated from the documentation by API Evangelist
    (2026-11-12); not the provider''s own document.'
  humanURL: https://imqueue.org/api/faq
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/imqueue-org-openapi-generated.yml
    x-provenance: generated
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: API documentation is public HTML but no OpenAPI, AsyncAPI, GraphQL, or other machine‑readable spec was found.
  evidence:
  - url: https://imqueue.org/api/
    status: 200
  checked: '2026-11-12'
x-enrichment:
  date: '2026-11-12'
  status: enriched
  artifacts_added: 21
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

@imqueue API — frequently asked questions

Does @imqueue have an API?

Yes. APIs.io lists 2 APIs from @imqueue, including Imqueue API and @imqueue API.

Is there an OpenAPI specification for the @imqueue API?

Yes. APIs.io indexes 1 OpenAPI specification for @imqueue, each linked for download from this page.

Is the @imqueue API ready for AI agents?

@imqueue has a Kin Score of 31.4 out of 100 (thin) and an Agent Readiness score of 15.5 (agent-aware), scored by API Evangelist on 2026-11-13.

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/imqueue-org"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/imqueue-org/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.