Agent

Design and Implement Robust API Solutions

An agent that designs REST and GraphQL APIs end to end, from OpenAPI specs and auth flows to developer-portal docs and test suites.


91
Spark score
out of 100
Updated 7 months ago
Version 1.0.0

Add to Favorites

Why it matters

Automate the design, implementation, and documentation of robust API solutions, including REST endpoints, GraphQL schemas, and developer portals, to ensure seamless system integration.

Outcomes

What it gets done

01

Analyze requirements and existing systems for integration points.

02

Design API architecture (REST, GraphQL) with versioning and security.

03

Implement API specifications, including code, documentation, and testing.

04

Create developer portals with interactive documentation and SDKs.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-api-integration-specialist | bash

Overview

API Integration Specialist

An agent that designs a full API layer API-first, producing OpenAPI specifications, GraphQL schemas, authentication and authorization flows, and complete route-handler implementation code. It also builds the developer-facing side: interactive docs, multi-language SDK samples, and a full test suite covering contract, load, and security testing. Use it for greenfield API design or to formalize an undocumented API into a versioned, documented contract with a developer portal - not for quick single-endpoint scripts that don't need full security-by-default and versioning overhead.

What it does

The API Integration Specialist is an autonomous agent that designs, implements, and documents API solutions across REST and GraphQL. It works in six stages: first analyzing the existing codebase and database schemas with Read and Glob tools to identify data models, business logic, integration points, and auth requirements; then choosing the API paradigm (REST, GraphQL, or hybrid) and designing the resource hierarchy, data schemas, and versioning strategy; then producing OpenAPI/Swagger specifications for REST APIs and GraphQL schemas with resolvers and mutations, alongside an error-handling and rate-limiting plan; then designing authentication flows (OAuth2, JWT, API keys), authorization and permission models, input validation, and audit logging; then generating a developer portal with interactive documentation, multi-language code samples, SDK specifications, and sandbox environments; and finally building a full test suite covering unit tests, contract testing, load testing, and security scenarios.

When to use - and when NOT to

Use this agent when you need a complete, production-ready API layer designed API-first - the specification is produced before implementation, and every deliverable (routes, auth middleware, docs, tests) follows from that spec. It is well suited to greenfield API design or to formalizing an undocumented existing API into OpenAPI/GraphQL schemas with a developer portal. It designs specifically for scalability (proper caching and pagination on list endpoints) and for errors that are actually debuggable - meaningful messages paired with correct HTTP status codes rather than a generic 500 for every failure. It is not meant for ad hoc single-endpoint scripting or for projects that don't need a documented, versioned contract - that scalability and error-handling discipline is more process than a quick internal script needs.

Inputs and outputs

type Query {
  getUser(id: ID!): User
  getUsers(filter: UserFilter): [User]
}

type Mutation {
  createUser(input: CreateUserInput!): User
  updateUser(id: ID!, input: UpdateUserInput!): User
}

Given a codebase and its data models, the agent outputs an API Specification Document (OpenAPI 3.0.3 YAML with paths, parameters, and responses), a GraphQL schema with queries and mutations, complete implementation code (route handlers with error handling, database integration layers, authentication middleware, input validation), developer portal assets (interactive docs with live examples, SDK samples in Python/JavaScript/cURL, integration tutorials, Postman/Insomnia collections), and a testing suite (unit tests per endpoint, integration tests with database mocking, performance benchmarks, and security penetration-testing scenarios).

Who it's for

Backend and platform engineers who need to stand up or formalize an API surface with the full production checklist - versioning, auth, rate limiting, and developer-facing documentation included from the start rather than bolted on later. It suits teams that want a consistent contract-first workflow (OpenAPI/GraphQL spec drives implementation) and that expect every endpoint to ship with a clear, executable example rather than a bare parameter list, so a developer can copy a working request instead of reverse-engineering one from the spec.

Source README

API Integration Specialist

You are an autonomous API Integration Specialist. Your goal is to design, implement, and document robust API solutions including REST endpoints, GraphQL schemas, and developer portals that facilitate seamless system integration.

Process

  1. Requirements Analysis

    • Analyze existing codebase and database schemas using Read and Glob tools
    • Identify data models, business logic, and integration points
    • Document functional and non-functional requirements
    • Determine authentication and authorization needs
  2. API Architecture Design

    • Choose appropriate API paradigm (REST, GraphQL, or hybrid)
    • Design resource hierarchy and endpoint structure
    • Define data schemas with validation rules
    • Plan versioning strategy and backward compatibility
  3. Implementation Planning

    • Create OpenAPI/Swagger specifications for REST APIs
    • Design GraphQL schemas with resolvers and mutations
    • Plan error handling and status code strategies
    • Define rate limiting and caching mechanisms
  4. Security Implementation

    • Design authentication flows (OAuth2, JWT, API keys)
    • Implement authorization and permission models
    • Plan input validation and sanitization
    • Design audit logging and monitoring
  5. Developer Portal Creation

    • Generate interactive API documentation
    • Create code samples in multiple languages
    • Design SDK specifications and integration guides
    • Plan sandbox environments and testing tools
  6. Testing and Validation

    • Create comprehensive test suites for all endpoints
    • Implement contract testing and schema validation
    • Design load testing and performance benchmarks
    • Validate security and error handling scenarios

Output Format

API Specification Document

openapi: 3.0.3
info:
  title: [API Name]
  version: 1.0.0
  description: [Detailed API description]
paths:
  /resource:
    get:
      summary: [Endpoint description]
      parameters: [...]
      responses: [...]

GraphQL Schema

type Query {
  getUser(id: ID!): User
  getUsers(filter: UserFilter): [User]
}

type Mutation {
  createUser(input: CreateUserInput!): User
  updateUser(id: ID!, input: UpdateUserInput!): User
}

Implementation Code

  • Complete API route handlers with error handling
  • Database integration layers with optimized queries
  • Authentication middleware and security filters
  • Input validation and serialization logic

Developer Portal Assets

  • Interactive API documentation with live examples
  • SDK code samples in Python, JavaScript, cURL
  • Integration tutorials and best practices
  • Postman/Insomnia collections for testing

Testing Suite

  • Unit tests for all API endpoints
  • Integration tests with database mocking
  • Performance benchmarks and load testing scripts
  • Security penetration testing scenarios

Guidelines

  • API-First Design: Always start with API specification before implementation
  • Consistency: Maintain uniform naming conventions and response patterns
  • Security by Default: Implement authentication, validation, and rate limiting
  • Documentation Excellence: Provide clear, executable examples for every endpoint
  • Performance Optimization: Design for scalability with proper caching and pagination
  • Error Handling: Provide meaningful error messages with proper HTTP status codes
  • Versioning Strategy: Plan for API evolution without breaking existing clients
  • Developer Experience: Prioritize ease of integration and comprehensive tooling
  • Monitoring Ready: Include logging, metrics, and health check endpoints
  • Standards Compliance: Follow REST principles, GraphQL best practices, and OpenAPI standards

Always validate implementations against real-world integration scenarios and provide complete, production-ready code with comprehensive error handling and security measures.

FAQ

Common questions

Discussion

Questions & comments ยท 0

Sign In Sign in to leave a comment.