Federal Laboratory Consortium for Technology Transfer

Federal Laboratory Consortium for Technology Transfer Sections API

The Sections API from Federal Laboratory Consortium for Technology Transfer — 1 operation(s) for sections.

Documentation GitHub OpenAPI

Operations 1

POST /v1/sections/search RAG search (mobile) #

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/federal-laboratory-consortium-for-technology-transfer-sections-api"

All apis

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

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.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Greenbook API (Public) Sections API
  description: Public API for mobile app (sync, sections stream, RAG search).
  version: '1.0'
  contact: {}
servers: []
tags:
- name: Sections
paths:
  /v1/sections/search:
    post:
      description: 'Retrieval-augmented answering: semantic retrieval, LLM rerank, then generated answer from top sections. Requires app-key header. Optional header: X-Session-Id (identifies mobile; used for metrics and queries-per-session). Returns answer plus source sections.'
      operationId: SectionsController_searchSections
      parameters:
      - name: x-session-id
        required: true
        in: header
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SectionSearchQueryDto'
      responses:
        '200':
          description: Generated answer and source sections ordered by relevance
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SectionSearchResponseDto'
      security:
      - app-key: []
      summary: RAG search (mobile)
      tags:
      - Sections
components:
  schemas:
    SectionSearchQueryDto:
      type: object
      properties:
        query:
          type: string
          description: Search query message (e.g. user question or topic)
          example: What are the penalties for tax evasion?
          maxLength: 2000
        limit:
          type: number
          description: 'Maximum number of sections to return (default: 10, max: 50)'
          default: 10
          minimum: 1
          maximum: 50
      required:
      - query
    SectionSearchResponseDto:
      type: object
      properties:
        answer:
          type: string
          description: RAG-generated answer based on retrieved sections
          example: According to the retrieved sections, penalties for tax evasion include...
        sections:
          description: Source sections used for the answer (reranked by LLM), ordered by relevance
          type: array
          items:
            $ref: '#/components/schemas/SectionSearchResultItemDto'
        cacheId:
          type: number
          description: Cache entry id; use this to submit feedback (accepted/rejected) via POST /v1/sections/query-cache/:id/feedback
          example: 42
      required:
      - answer
      - sections
    SectionSearchResultItemDto:
      type: object
      properties:
        section:
          type: object
          description: Section id and title only
        score:
          type: number
          description: Similarity score (0–1, higher = more similar)
          example: 0.87
      required:
      - section
      - score
  securitySchemes:
    bearer:
      scheme: bearer
      bearerFormat: JWT
      type: http
    app-key:
      type: apiKey
      in: header
      name: app-key
      description: Mobile app key (for sync-sections, mobile-app-sections, search)