akili rid

Manage Resource Identifiers (RIDs) on the Akili platform. Every entity in the platform — products, tables, columns, connections, serving stores — has a globally unique RID that follows the format akili:<type>:<name>. RIDs provide a stable addressing scheme for cross-referencing entities across the platform.

Commands

akili rid resolve <rid>

Resolve a Resource Identifier to its full metadata including resource type, name, and owning product.

Arguments:

Argument	Type	Required	Description
rid	string	yes	RID string (e.g., akili:product:daily-orders)

Examples:

# Resolve a product RID
akili rid resolve akili:product:daily-orders

# Resolve a table RID
akili rid resolve akili:table:sales.daily_order_summary

# As JSON
akili rid resolve akili:product:daily-orders --json

---

akili rid list

List all Resource Identifiers, optionally filtered by product or resource type.

Flags:

Flag	Short	Default	Description
--product			Filter by product ID
--type			Filter by resource type (e.g., product, table, column, connection)

Examples:

# List all RIDs
akili rid list

# List RIDs for a specific product
akili rid list --product prod-abc123

# List only table-type RIDs
akili rid list --type table

# Combine filters
akili rid list --product prod-abc123 --type column

# As JSON
akili rid list --json

---

akili rid children <rid>

List all child resources of a given RID. For example, a product RID’s children include its tables, and a table RID’s children include its columns.

Arguments:

Argument	Type	Required	Description
rid	string	yes	Parent RID string

Examples:

# List children of a product (tables, views)
akili rid children akili:product:daily-orders

# List children of a table (columns)
akili rid children akili:table:sales.daily_order_summary

---

akili rid lineage <rid>

Show the full lineage chain for a Resource Identifier. Traces the resource’s provenance through the dependency graph, from upstream sources through transformations to downstream consumers.

Arguments:

Argument	Type	Required	Description
rid	string	yes	RID string

Examples:

# Trace lineage for a product
akili rid lineage akili:product:daily-orders

# As JSON for programmatic analysis
akili rid lineage akili:product:daily-orders --json

---

RID Format

Resource Identifiers follow a hierarchical naming convention:

akili:<resource_type>:<qualified_name>

Resource Type	Format	Example
product	akili:product:<name>	akili:product:daily-orders
table	akili:table:<namespace>.<name>	akili:table:sales.daily_order_summary
column	akili:column:<namespace>.<table>.<col>	akili:column:sales.daily_order_summary.revenue
connection	akili:connection:<name>	akili:connection:production-db
serving	akili:serving:<product>.<intent>	akili:serving:daily-orders.analytics

RIDs are tenant-scoped — the same RID string in different tenants refers to different resources.

Global Flags

All akili rid commands support these global flags:

Flag	Short	Default	Description
--json		false	Output as JSON instead of tables
--profile		default	Config profile to use
--api-url		from config	API base URL override
--timeout		30	Request timeout in seconds