API

    Rawxel API for sourcing execution.

    Build against raw materials sourcing workflows: specs, suppliers, auctions, bids, comparisons, and awards. Use OpenAPI directly, or add the MCP config when an agent needs controlled access.

    Rawxel API

    Structured sourcing, not a scraped UI.

    OpenAPI schema

    Machine-readable API contract for codegen and client setup.

    API docs

    Interactive Rawxel core endpoints for sourcing workflows.

    llms.txt

    Plain-text capability map and approval boundary.

    Sourcing API flow

    1

    Create a sourcing event

    Send specs, dates, suppliers, and auction rules.

    2

    Invite suppliers

    Attach known suppliers or email invitees.

    3

    Run bids

    Submit bids and read rank-aware status.

    4

    Compare responses

    Fetch comparable bids, documents, terms, and history.

    5

    Award

    Move from evaluation to a buyer-approved award.

    MCP setup

    Keep secrets in rawxel-core/.env. The client only needs to launch the server from the repo.

    {  "mcpServers": {    "rawxel": {      "command": "uv",      "args": [        "--directory", "/absolute/path/to/rawxel-core",        "run", "python", "-m", "app.mcp_server"      ]    }  }}

    Human approval boundary

    Agents draft and compare. They ask before irreversible sourcing, bidding, award, and post-award commitments.

    • Publish auctions
    • Invite suppliers
    • Start live bidding
    • Submit bids
    • Close auctions
    • Award suppliers
    • Accept contract, PO, payment, or dispatch commitments