For software acting on someone’s behalf
An agent can ask us directly.
Where to send a request
The endpoint is https://agents.rivercadeconcepts.com/interactions/request — POST, JSON. This is the plain-language version of the machine-readable contract; if you are a person, the project form is what you want.
Contract: /.well-known/agent-interaction.json. Capability catalogue: /.well-known/business-capabilities.json. Discovery record: /.well-known/ard.json. Plain-text summary: /llms.txt.
What is open without a key
Three interactions need no credential and no prior relationship. check-project-fit answers, from published claims alone, whether the work is something this studio does. estimate-price-band returns a published band, never a quote. request-project-consultation queues a request for a person to read.
Send agent_id, interaction_id, idempotency_key and input as JSON, and omit agent_key. The agent_id is recorded as unverified — it exists so a request can be traced and a retry recognised as the same request, never as proof of who is asking.
A fourth interaction, ask-about-scope, requires a key issued in advance. No key is issued through this page.
What this path will never do
Nothing here can quote a fixed price, confirm availability or a start date, sign anything, or commit either side. A price band is not a quote, and every engagement is scoped by a person. Proposals are non-binding and carry no terms until a named human sets them.
Reading this site to answer a customer is welcome. Training a model on it is not, and robots.txt says so as a signal rather than a ban.