Claude Haiku via x402 Gateway

{
  "model": "claude-haiku-3-5",
  "messages": [
    {
      "role": "user",
      "content": "Summarize the key differences between REST and GraphQL in 3 bullet points"
    }
  ],
  "max_tokens": 256
}

{
  "model": "anthropic/claude-4.5-haiku-20251001",
  "usage": {
    "cost": 0.000739,
    "is_byok": false,
    "cost_details": {
      "upstream_inference_cost": 0.000739,
      "upstream_inference_prompt_cost": 0.000024,
      "upstream_inference_completions_cost": 0.000715
    },
    "total_tokens": 167,
    "prompt_tokens": 24,
    "completion_tokens": 143,
    "prompt_tokens_details": {
      "audio_tokens": 0,
      "video_tokens": 0,
      "cached_tokens": 0,
      "cache_write_tokens": 0
    },
    "completion_tokens_details": {
      "audio_tokens": 0,
      "image_tokens": 0,
      "reasoning_tokens": 0
    }
  },
  "content": "# REST vs GraphQL: Key Differences\n\n• **Data Fetching**: REST returns fixed data structures (over-fetching or under-fetching), while GraphQL lets clients request exactly what they need, reducing bandwidth and improving efficiency.\n\n• **Endpoints**: REST uses multiple endpoints for different resources (e.g., `/users`, `/posts`), whereas GraphQL typically uses a single endpoint where queries specify the required data structure.\n\n• **Flexibility & Learning Curve**: GraphQL offers greater flexibility for complex queries and evolving client needs, but has a steeper learning curve; REST is simpler and more widely understood but less adaptable to varying client requirements."
}