Skip to content

Valont for agents

Published facts, fit assessment, a decision brief for the owner and, with consent, a callback request. Over MCP, a JSON API, A2A and WebMCP. We serve documents and structured facts. We never give advice.

View the endpointsBook a consult

17

Tools, one write

No key

MCP, JSON API, A2A

Facts

Never advice

QLD

Governing law

The step from information to advice is a conversation with a person. Every response is general information only, quoted from published pages with its URL and date. No fee bands are published, so no tool returns a price. The one write, a callback request, needs the owner’s explicit consent and commits nobody to anything: scope and price are confirmed with a person.

The MCP endpoint

The server is live using the MCP streamable HTTP transport. Point any MCP-compatible client at the URL and call tools/list to discover the tools.

Endpoint

https://www.valont.com.au/api/mcp/mcp

Search and retrieve

Search and retrieve Valont’s published insights, answers and industry pages.

  • search_content
  • get_explainer
  • list_content
  • find_industry

Look up facts

Structured facts already published on the site, each quoted with its URL and date. Where two published statements differ, both are returned.

  • get_facts
  • get_award_summary
  • get_glossary_term
  • get_local_facts
  • get_ai_capability

Qualify and decide

Whether a business fits Valont’s published service area and size range, which services match the need, and a decision brief the agent can take back to the owner.

  • assess_fit
  • get_decision_brief
  • describe_services
  • get_indicative_fee

Book a conversation

How the booking page works, and, with the owner’s explicit consent, a callback request lodged through the same form, with a reference the agent can check.

  • get_booking_link
  • book_consult
  • request_callback
  • get_request_status

Every door leads to the same desk

One tool registry serves every interface, so an agent gets the same facts, sources and disclaimer whichever way it arrives.

  • MCP serverhttps://www.valont.com.au/api/mcp/mcpStreamable HTTP transport, no API key. Point any MCP client at the URL and call tools/list.
  • HTTP JSON APIhttps://www.valont.com.au/api/agent/v1/toolsThe same tools as plain JSON over HTTPS for agents without an MCP client. POST /tools/{name} with a JSON body; aliases for /facts, /fit, /brief, /callback and /requests/{id}.
  • OpenAPI 3.1https://www.valont.com.au/api/agent/v1/openapi.jsonGenerated from the same tool registry as the MCP server, so the two cannot disagree.
  • A2A agent cardhttps://www.valont.com.au/.well-known/agent-card.jsonAgent2Agent protocol. JSON-RPC endpoint at /api/a2a with message/send and tasks/get.
  • WebMCPOn every pageWhere a browser exposes the model context API, pages register the front-desk tools so a browsing agent can call them instead of scraping.
  • Discovery/llms.txt, /catalogue.json, /.well-known/api-catalogThe plain-text summary, the offer catalogue and the RFC 9727 API catalogue all point here.

The safety design

  • One source of truthThe interface serves only content already published and approved on valont.com.au, read from the same data files the site renders. There are no agent-only facts or claims. Insight articles reach the pages, the /insights.json feed and the content tools through one shared accessor.
  • No adviceNo personalised tax, BAS, financial, HR or legal recommendations are produced by any tool. Calculations run on the figures you provide and remain general information.
  • Provenance on everythingEach response carries its canonical source URL(s) and a “current as at” date so you and your users can verify it.
  • We do not fill gapsWhere Valont holds no verified, published data for a request, the tool says so and points to the primary source, such as the Fair Work Commission or the ATO. It never estimates or interpolates.
  • One write, with consentThe only tool that writes anything is request_callback. With the person’s explicit consent (consent=true) it lodges a callback request through the same form as the booking page and records the stated needs for the advisor. Nothing else changes Valont content, a CRM record or a booking. A callback request is a request for a conversation; scope and price are confirmed with a person.

API terms of use

Last updated: 13 October 2026

  • 1. AcceptanceBy accessing Valont’s agent interface or APIs (the “Service”), you agree to these terms. If you access the Service on behalf of an organisation, you do so with its authority.
  • 2. LicenceValont grants you a non-exclusive, revocable, non-transferable licence to query the Service and to display its responses to your users, provided the source attribution and the “general information only, not advice” disclaimer accompanying each response are preserved and not altered or removed.
  • 3. No advice; no relianceAll responses are general information only and do not constitute financial, tax, accounting, legal or other professional advice, and are not tailored to anyone’s circumstances. Pricing returned is indicative only and is not a quote or an offer. Valont cannot be bound to any engagement, scope or price through the Service. You must not present Service responses as advice or as a Valont commitment.
  • 4. Acceptable useYou must not: use the Service to provide regulated advice; misrepresent Valont, its services, pricing or claims; scrape or harvest beyond ordinary use or to reconstruct the underlying datasets; attempt to circumvent rate limits, access controls or the disclaimer; or use the Service unlawfully or to harm others.
  • 5. Availability and changesThe Service is provided on an “as is” and “as available” basis. Valont may change, suspend, deprecate (with reasonable notice where practical) or withdraw the Service or any tool at any time. Schemas are version-stamped; breaking changes are deprecated with an overlap window where practical.
  • 6. LiabilityTo the maximum extent permitted by law, Valont is not liable for any loss arising from use of, or reliance on, the Service. Nothing in these terms excludes rights or guarantees under the Australian Consumer Law that cannot lawfully be excluded.
  • 7. Governing lawThese terms are governed by the laws of Queensland, Australia, and you submit to the non-exclusive jurisdiction of its courts.
  • 8. Contacthello@valont.com.au

Privacy, agent interface

Last updated: 13 October 2026

  • Intent, not identityTo improve the Service we log the tool called and its parameters, the consuming client’s technical metadata where available, and aggregate usage signals. We do not store end-user identifiers or conversation transcripts beyond the request parameters.
  • PII minimisationFree-text parameters are scrubbed for personal information. Raw request logs are retained for up to 90 days and then reduced to non-identifying aggregates.
  • Consult bookingsIf you book a consult and choose to pass a context summary, that summary is retained in Valont’s CRM under Valont’s standard privacy policy so a human advisor can prepare. This is the one consented exception to the minimisation above.
  • No payment dataNo payment data is collected through the Service. We handle personal information consistently with the Australian Privacy Principles and our main Privacy Policy.

These developer terms and privacy note sit alongside, and do not replace, Valont’s main Terms and Privacy Policy.

Need a human, not an endpoint?

The MCP server returns facts. A Trusted Advisor conversation is where advice starts.

Book a consultRead the editorial policy