WritersLogic Verifiable AI Agent Hub Micro Batch API

The Micro Batch API from WritersLogic Verifiable AI Agent Hub — 1 operation(s) for micro batch.

GitHub OpenAPI

Operations 1

POST /api/v1/micro-batch Run up to 20 micro checks under one payment ($0.02) #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/writerslogic-com:writerslogic-com-micro-batch-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

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.

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

OpenAPI Specification

writerslogic-com-micro-batch-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: WritersLogic Verifiable AI Agent Hub Micro Batch API
  version: 2.0.0
  description: Pay-per-call agents settled in USDC on Base via x402. Every response carries a signed provenance envelope.
  contact:
    name: WritersLogic
    url: https://writerslogic.com/agents
    email: agents@writerslogic.com
servers:
- url: https://agents.writerslogic.com
tags:
- name: Micro Batch
paths:
  /api/v1/micro-batch:
    post:
      operationId: micro_batch
      summary: Run up to 20 micro checks under one payment ($0.02)
      description: 'Bundles up to 20 calls to any pure micro check (catalog entries that are neither stateful nor network-reading, e.g. checksum, patch-anchor, allocate, business-deadline) into one x402 settlement, so a full batch costs $0.001 per check. Every call is validated before payment; one invalid call rejects the batch with its index. The request is capped at 128kb and a CPU weight of 40 (an ordinary check weighs 1; dst-check 5, time-bucket-check 5, float-stability 2, font-convert 20, font-glyph-svg 3, font-face-css 3). Results come back in order, each exactly as the single-call endpoint returns it.


        Price: 0.02 USDC on Base (x402).'
      x-x402-price-usdc: '0.02'
      x-x402-amount: '20000'
      x-payment-info:
        protocols:
        - x402
        price:
          mode: fixed
          currency: USD
          amount: '0.02'
      x-audience: agent-infra
      x-sample-url: https://agents.writerslogic.com/api/v1/samples/micro-batch
      security:
      - x402: []
      - apiKey: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              additionalProperties: false
              required:
              - calls
              properties:
                calls:
                  type: array
                  minItems: 1
                  maxItems: 20
                  items:
                    type: object
                    additionalProperties: false
                    required:
                    - tool
                    - input
                    properties:
                      tool:
                        type: string
                        pattern: ^[a-z0-9]+(-[a-z0-9]+)*$
                        description: Micro check id, e.g. checksum.
                      input:
                        type: object
                        description: That check's own request body.
            example:
              calls:
              - tool: acceptance-receipt
                input:
                  output:
                    total: 10
                  tests:
                  - id: positive
                    kind: number-between
                    path: /total
                    min: 0
              - tool: acceptance-receipt
                input:
                  output:
                    total: -1
                  tests:
                  - id: positive
                    kind: number-between
                    path: /total
                    min: 0
      responses:
        '200':
          description: Paid result with provenance
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      status:
                        type: string
                        enum:
                        - pass
                        - fail
                        - unknown
                        - unsupported
                        description: 'pass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.'
                      calls:
                        type: integer
                      counts:
                        type: object
                        properties:
                          pass:
                            type: integer
                          fail:
                            type: integer
                          unknown:
                            type: integer
                          unsupported:
                            type: integer
                      results:
                        type: array
                        items:
                          type: object
                          properties:
                            index:
                              type: integer
                            tool:
                              type: string
                            response:
                              type: object
                              description: Exactly what the single-call endpoint returns.
                      witnesses:
                        type: array
                        items:
                          type: object
                          properties:
                            ruleId:
                              type: string
                            detail:
                              type: string
                            path:
                              type: string
                              description: JSON pointer or dotted path into the input.
                            offset:
                              type: integer
                            index:
                              type: integer
                            expected:
                              description: What the rule required.
                            actual:
                              description: What the input had.
                      versions:
                        type: object
                        description: Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
                      limits:
                        type: array
                        items:
                          type: string
                      deterministic:
                        type: boolean
                        description: 'Always true: pure code, no model.'
                  _provenance:
                    type: object
                    description: C2PA-aligned manifest and W3C VC 2.0 (eddsa-jcs-2022) issued by the hub DID; verify at POST /api/v1/verify-provenance
                required:
                - data
                - _provenance
        '400':
          description: Invalid request (no payment consumed)
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
        '401':
          description: Invalid X-API-KEY
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
        '402':
          description: Payment required or invalid
          content:
            application/json:
              schema:
                type: object
                description: x402 v2 PaymentRequired (also base64 in the PAYMENT-REQUIRED header)
                properties:
                  x402Version:
                    type: integer
                  error:
                    type: string
                  code:
                    type: string
                  resource:
                    type: object
                  accepts:
                    type: array
                    items:
                      type: object
                  extensions:
                    type: object
        '502':
          description: Upstream failure; the payment is released or not settled
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
      tags:
      - Micro Batch
components:
  securitySchemes:
    x402:
      type: apiKey
      in: header
      name: PAYMENT-SIGNATURE
      description: x402 v2 payment payload (base64) sent after a 402 challenge
    apiKey:
      type: apiKey
      in: header
      name: X-API-KEY