For Agents
Programmatically query the squiggle api for various data types. Covers 1 operations.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Squiggle AFL API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsquiggle.com.au%2Fsquiggle-com-au" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsquiggle.com.au%2Fsquiggle-com-au" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Squiggle AFL API.
Query the Squiggle API for various data types
Manage crm data programmatically
Integrate Squiggle AFL API into automated workflows
Query and filter Squiggle AFL API records by parameters
GET STARTED
Use for: I need to query the squiggle api for various data types, Find available crm operations, Get the current status of Squiggle AFL API resources, List all records from Squiggle AFL API
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
The Squiggle API provides AFL (Australian Football League) data including teams, games, tips, standings, ladder projections, and power rankings. No authentication is required but a descriptive User-Agent header identifying your application and contact information is mandatory. The API exposes 1 endpoints.
Monitor Squiggle AFL API operational status and events
Patterns agents use Squiggle AFL API for, with concrete tasks.
★ CRM Operations
Use the Squiggle AFL API to perform crm operations programmatically. The API provides 1 endpoints covering core functionality including query the squiggle api for various data types.
Call GET / to query the squiggle api for various data types
Data Retrieval and Monitoring
Query Squiggle AFL API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Squiggle AFL API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Squiggle AFL API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'query the squiggle api for various data types', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — the squiggle api provides afl (australian football league) data including teams, games, tips, standings, ladder projections, and power rankings.
METHOD
PATH
DESCRIPTION
/
Query the Squiggle API for various data types
/
Query the Squiggle API for various data types
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Squiggle AFL API by hand means reading its docs to learn the single query endpoint on api.squiggle.com.au and the parameters that select each data type yourself. Through Jentic you install once, import the Squiggle AFL API from the API Directory, and your agent calls it, since this API needs no credential.
Permission scoping
This API exposes one read-only query operation, so you can limit the agent to that single call: it fetches the AFL data you ask for and can do nothing else.
Credential isolation
The Squiggle AFL API needs no credential, so there is nothing to store, and no secret ever enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get AFL fixtures' or 'fetch the current ladder', and Jentic returns the matching Squiggle AFL API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Squiggle AFL API through Jentic.
What authentication does the Squiggle AFL API use?
The Squiggle AFL API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I query the squiggle api for various data types with the Squiggle AFL API?
Yes. Use the GET / endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Squiggle AFL API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I query the squiggle api for various data types through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'query the squiggle api for various data types'. Jentic returns the matching Squiggle AFL API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Squiggle AFL API have?
The Squiggle AFL API exposes 1 endpoints covering teams, games, sources operations.