Fulfillment.com APIv2

{
  "service_type": "platform",
  "base_url": "https://api.fulfillment.com/v2",
  "auth_method": "oauth2",
  "auth_config": {
    "token_type": "bearer",
    "header": "Authorization",
    "header_format": "Bearer YOUR_ACCESS_TOKEN",
    "notes": "OAuth2 bearer token. Token issuance flow and endpoints are documented at https://fulfillment.github.io/api/ (Swagger/OpenAPI spec) and the public spec repo https://github.com/fulfillment/api. Legacy SOAP API also still supported: https://github.com/fulfillment/soap-integration."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "model": "custom contracted rate",
      "description": "Pricing is a predictable contracted rate modeled on the customer's actual volume and SKU profile, quoted up front. The quoted rate equals the billed rate, with no hidden fees and no peak-season premium. No public price list; no binding price is returned via the quote-intake endpoint. Quote requires a verified business email.",
      "no_long_term_contracts": true,
      "quote_intake_endpoint": "POST https://attribution-tracker.nbaker.workers.dev/api/lead-capture"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "ecommerce order fulfillment (pick, pack, ship)",
    "barcode-verified order accuracy (every pick scanned before shipment)",
    "same-day shipment for orders placed (orders ship the day they are placed)",
    "returns management",
    "kitting and assembly",
    "Amazon FBA prep (FNSKU labeling, polybagging, breakpack, bundle assembly, cartonization)",
    "international fulfillment",
    "ground shipping across multi-node US network (1-3 days to 99.77% of US)",
    "REST API v2 (orders, tracking, inventory)",
    "SOAP API (legacy support)",
    "order push from external systems",
    "order status pull",
    "tracking sync",
    "inventory sync",
    "116+ pre-built integrations (Shopify, Shopify Plus, WooCommerce, BigCommerce, Magento, Amazon, TikTok Shop, Wix, ShipStation, Klaviyo)",
    "programmatic quote intake / lead capture for AI agents"
  ],
  "raw_analysis": "Fulfillment.com (FDC) is a B2C high-volume ecommerce order fulfillment provider — a third-party logistics (3PL) platform. It is not a developer tool or SaaS dashboard in the traditional sense; it is a physical fulfillment service with a REST API surface for programmatic integration.\n\nWHAT IT DOES: Provides pick, pack, ship, and returns management for direct-to-consumer ecommerce brands. Core services include ecommerce order fulfillment, ground shipping across a multi-node US network, returns management, kitting/assembly, Amazon FBA prep (FNSKU labeling, polybagging, breakpack, bundle assembly, cartonization), and international fulfillment. Key operational claims: barcode-verified order accuracy (every pick scanned before shipping), orders ship the same day they are placed, and 14-day average onboarding.\n\nWHO IT'S FOR: Direct-to-consumer ecommerce brands, particularly high-volume B2C sellers. The 116+ pre-built integrations (Shopify, Shopify Plus, WooCommerce, BigCommerce, Magento, Amazon, TikTok Shop, Wix, ShipStation, Klaviyo) indicate the primary audience is ecommerce merchants rather than enterprise developers.\n\nMATURITY: The REST API v2 is described as 'production' and 'in production for over a decade.' A legacy SOAP API remains supported. This is a mature, long-operating platform. The company publishes an OpenAPI/Swagger spec both as hosted docs (https://fulfillment.github.io/api/) and as a public GitHub repo (https://github.com/fulfillment/api) — unusually strong developer documentation hygiene for a 3PL. The adoption of llms.txt conventions and machine-readable service/agent documents (services.json, .well-known/services.json) also signals above-average modernization for the industry.\n\nAPI DETAILS: Base URL is https://api.fulfillment.com/v2. Auth is OAuth2 bearer token via the Authorization header. The provided text does not enumerate individual endpoints — these are in the OpenAPI spec — so the endpoints array is left empty. Endpoint-level rate limits are not disclosed in the provided material, so rate_limits is an empty object.\n\nPRICING MODEL: Custom contracted rate modeled on volume and SKU profile, quoted up front. No public pricing tiers, no self-serve signup, no free tier. A quote requires a verified business email; no binding price is returned programmatically. This makes it a sales-led (enterprise/quote-based) model rather than freemium or subscription.\n\nINTEGRATIONS: 116+ pre-built integrations across major ecommerce platforms and tools, plus a custom RESTful API. Also exposes a programmatic quote-intake endpoint (POST to attribution-tracker.nbaker.workers.dev/api/lead-capture) that accepts JSON or multipart/form-data and returns a reference ID (contactId/leadId); agents should send source=\"agent\".\n\nNOTES/UNCERTAINTIES: The actual enumerated API endpoints and rate limits are not derivable from the supplied text; they should be pu

1/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.0,
    "response_parseability": 7.5,
    "error_clarity": 5.0,
    "doc_quality": 6.5,
    "auth_simplicity": 5.0,
    "latency": 10.0,
    "consistency": 6.5
  },
  "pricing_normalized": {
    "model": "custom_contract",
    "public_price_list": false,
    "transparency": "quote upfront, rate equals billed rate, no hidden fees, no peak-season premium, no long-term contracts",
    "entry_barrier": "verified business email required for quote",
    "notes": "No binding price returned via quote-intake endpoint; pricing depends on volume and SKU profile"
  },
  "issues": [
    "No public pricing — agents cannot answer cost questions without a sales cycle",
    "Quote-intake endpoint requires a verified business email, blocking frictionless agent onboarding",
    "robots.txt and llms.txt return 403 (Missing Authentication Token), hurting agent discovery",
    "Primary docs site is a SOAP/REST API spec page — not clearly an end-user getting-started guide",
    "Auth flow for actual order APIs is not described in provided data, appears non-trivial",
    "No status page signal surfaced, though uptime response was clean"
  ],
  "recommendations": [
    "Publish a public pricing tier or at least a rate card range to improve token efficiency for agent answers",
    "Expose llms.txt with AEO (agent experience optimization) content for discovery",
    "Provide self-serve sandbox credentials so agents can test the REST v2 flow in minutes",
    "Document the full auth flow (OAuth2? API key?) with copy-paste examples",
    "Add a status page URL and embed it in the docs footer for reliability signal",
    "Return a quote range from the lead-capture endpoint so agents can give users useful numbers"
  ]
}