================================================================================
FULLY EQUIPPED MACHINERY - PARTNER INVENTORY API
COPY-PASTE PROMPT FOR YOUR AI ASSISTANT
================================================================================

HOW TO USE THIS
1. Replace the two lines marked  <<< FILL THIS IN >>>  with your own details.
2. Copy everything between the START and END markers.
3. Paste it into ChatGPT, Claude, Cursor, GitHub Copilot, Lovable, Replit, or
   whichever AI tool builds or edits your website.
4. Answer any questions it asks about your site, then follow its instructions.

DO NOT paste your API key into a public chat, a shared document, or any tool
your competitors can read. If you are unsure, use the placeholder text
FEM_API_KEY and set the real key as an environment variable on your server, as
the prompt below instructs.

================================================================================
----------------------------- START COPYING HERE -----------------------------

I am an independent equipment dealer. I want to display Fully Equipped
Machinery's used excavator inventory and attachment product line on my own
website, using their Partner Inventory API. Please build this integration for
me.

MY SETUP
- My website is built with: <<< FILL THIS IN: e.g. WordPress, Shopify, Wix,
  Squarespace, Next.js, plain HTML, custom PHP >>>
- My site is hosted on: <<< FILL THIS IN: e.g. GoDaddy, SiteGround, Vercel,
  Netlify, my own server >>>

Before writing any code, ask me anything you need to know about my setup, and
tell me plainly if my platform cannot do what this integration requires.

=== THE API ===

Base URL:  https://fullyequippedmachinery.com/api/partners/v1

Authentication: every request needs this header, where FEM_API_KEY is a secret
key Fully Equipped Machinery issued to me and I will supply separately:

    Authorization: Bearer FEM_API_KEY

The key is NOT accepted in a query string. It must be sent as a header.

ENDPOINTS I WANT TO USE

  GET /machines
      Every used machine currently available, at Fully Equipped Machinery's
      retail price. This is the main one. Returns:
      {
        "count": 4,
        "generated_at": "2026-08-12T00:00:00.000Z",
        "machines": [
          {
            "id": "1",
            "fem_url": "https://fullyequippedmachinery.com/equipment/...",
            "year": 2021,
            "make": "Hitachi",
            "model": "ZX135USK-6",
            "hours": 2950.3,
            "ton_class": "13.5 Ton",
            "status": "available",
            "location": "Surrey BC",
            "price": { "basis": "retail", "cad": 159000, "usd": 112900 },
            "specifications": {
              "equipmentType": "Excavator",
              "auxHydraulics": "Yes - lines plumbed to arm end",
              "engineManufacturer": "Isuzu",
              "engine": "AR-4JJ1X (Isuzu 4JJ1)",
              "engineFamily": "Pending verification",
              "power": "78.5 kW (105 hp)",
              "emissions": "US EPA Tier 4 Final"
            },
            "installed_equipment": ["Hydraulic quick coupler", "Hydraulic thumb"],
            "shipping": null,
            "photos": [
              {
                "url": "https://fullyequippedmachinery.com/api/catalog-media/1/0",
                "alt": "Hitachi ZX135USK-6 - photo 1",
                "kind": "finished_photo",
                "sort": 0
              }
            ]
          }
        ]
      }

  GET /machines/{id}
      One machine by its id. Returns 404 if that unit is no longer available.

  GET /attachments
      Attachment product line - buckets, thumbs, couplers, breakers,
      tilt-rotators - grouped into families, each with its SKUs at list price.
      Returns:
      {
        "count": 42,
        "sku_count": 225,
        "families": [
          {
            "id": "excavator-buckets-digging-bucket",
            "name": "Digging Bucket",
            "segment": "excavator",
            "category": "Buckets",
            "description": "...",
            "variants": [
              {
                "sku": "FEMCUB1015",
                "label": "10-15T",
                "carrier_class": "10-15T",
                "price": { "basis": "retail", "cad": 6298, "usd": 4999 }
              }
            ]
          }
        ]
      }

  GET /me
      Confirms my key works and reports its permissions. Use this first to
      verify the connection before building anything else.

ENDPOINTS TO IGNORE
There are also /machines/pricing and /attachments/pricing endpoints. They
return my confidential cost and commission. DO NOT call them from my website
and DO NOT build anything that displays them. They are for my back office only.

=== HARD RULES - THESE ARE NOT OPTIONAL ===

1. THE API KEY MUST NEVER REACH THE BROWSER.
   Call the API from my server, never from client-side JavaScript. Do not put
   the key in a React component, an inline <script>, a data attribute, or any
   file the browser downloads. Anyone can read those, and a leaked key gets
   revoked.
   - Store the key in an environment variable or my platform's secret store.
   - If my platform genuinely cannot make server-side requests, STOP and tell
     me that plainly instead of putting the key in the browser. Suggest a
     workaround such as a scheduled job that writes the data to a static file.

2. DISPLAY THE RETAIL PRICE EXACTLY AS RETURNED.
   Use the `price.cad` and `price.usd` values as they come. Do not add a
   markup, do not recalculate, do not round. My margin is handled separately
   between me and Fully Equipped Machinery; the price on my website must match
   theirs.

3. CACHE FOR 5 MINUTES. DO NOT POLL IN A LOOP.
   Cache each response for 300 seconds and reuse it. My key is limited to 1200
   requests per hour and every response includes X-RateLimit-Remaining. A page
   that calls the API on every visitor load will blow through the limit.

4. HOTLINK THE PHOTOS. DO NOT DOWNLOAD AND RE-HOST THEM.
   Use the photo `url` values directly in my <img> tags. They are already
   absolute URLs. If Fully Equipped Machinery corrects or withdraws a photo,
   hotlinking means my site picks up the change automatically.

5. NEVER INVENT INVENTORY.
   Only show machines the API actually returns. If the API returns 4 machines,
   show 4. Do not use placeholder or sample machines anywhere in the live site.
   Sold machines disappear from the response - that is intentional, and my page
   must handle the list shrinking.

6. FAIL QUIETLY AND VISIBLY TO ME, NOT TO MY CUSTOMERS.
   If the API is unreachable or returns an error, show the last cached data if
   available, otherwise hide the section entirely. Never show a raw error, a
   stack trace, or an empty broken grid to a visitor. Log the error where I can
   find it.

=== WHAT I WANT BUILT ===

a) A server-side function that fetches from the API with my key, with the
   5-minute cache and sensible error handling.

b) An inventory listing page showing all available machines as cards: primary
   photo, year, make, model, hours, ton class, location, and retail price.

c) A detail page or modal for a single machine: the full photo gallery,
   specifications, and installed equipment.

d) An attachments page grouped by family, with each family's SKUs, carrier
   class and list price in a table.

e) An inquiry form on each listing that sends the enquiry TO ME, with the
   machine's id, year, make and model attached so I know what they are asking
   about. Leads are mine; do not send them to Fully Equipped Machinery.

f) A "Sourced by Fully Equipped Machinery" credit on any page showing this
   inventory. This is required by my agreement with them.

=== HOW TO PROCEED ===

1. Tell me what you need to know about my site before you start.
2. Show me where to put the API key on my specific platform, step by step, as
   if I am not a developer.
3. Give me the complete code, file by file, with the full path of each file and
   whether I am creating it or editing it.
4. Give me a way to test the connection first - a single call to /me that
   prints the result - so I can confirm the key works before building pages.
5. Tell me exactly how to verify each piece works once installed.

Explain each step in plain language. Assume I can copy and paste files and
follow instructions, but that I am not a programmer and cannot debug code on
my own.

------------------------------ END COPYING HERE ------------------------------
================================================================================

IF YOUR AI GETS STUCK

Paste the exact error message back to it and ask it to fix the specific
problem. If it keeps failing, tell it:

    "Start over with the simplest possible version: one server-side page that
     calls GET /me and prints the JSON response. Nothing else."

Once that works, add the machines listing, then the detail pages, then the
attachments, one at a time.

Still stuck? Email sales@fullyequippedmachinery.com with what you tried and the
error you are seeing, and we will help.

================================================================================
Fully Equipped Machinery  |  Smiler Equipment Ltd.
sales@fullyequippedmachinery.com  |  1 888-334-6467
https://fullyequippedmachinery.com/developers
================================================================================