Agent Proposals
Connector: people (https://swapi.info/api/) ← connector
StarWarsCharacter
Represents a character from the Star Wars universe, including physical attributes, biographical details, and associations with films, species, vehicles, and starships, as sourced from the SWAPI dataset.
Display label: name
Potential relationships detected:
The source data clearly represents Star Wars characters from the SWAPI (Star Wars API), containing biographical and physical attributes (name, height, mass, hair/skin/eye color, birth year, gender), relational URL references to homeworld, films, species, vehicles, and starships, and metadata timestamps. This is distinct from the existing Employee entity type which is organization-focused. The entity is named StarWarsCharacter to be descriptive and domain-specific. Fields like height and mass are kept as strings since they contain non-numeric placeholders ('n/a'). The homeworld, films, species, vehicles, and starships fields are URL-based foreign-key-style references to other SWAPI resource types, making them strong candidates for relationships.
Connector: films (https://swapi.info/api/) ← connector
StarWarsFilm
Represents a Star Wars film entry from the SWAPI dataset, including metadata such as title, episode number, director, producer, release date, opening crawl text, and references to associated characters, planets, starships, vehicles, and species.
Display label: title
Potential relationships detected:
The source data clearly represents Star Wars film entries from the SWAPI (Star Wars API). Each record has a unique title, episode ID, opening crawl, director, producer, release date, and multiple relationship arrays (characters, planets, starships, vehicles, species) stored as lists of resource URLs. The existing Employee entity type is entirely unrelated. A dedicated StarWarsFilm entity type captures all fields faithfully, with json arrays for the multi-valued relationship fields and appropriate scalar types for the remaining fields. The relationship arrays contain URLs pointing to other SWAPI resource types, signaling foreign-key-style references to separate entity types.
Ingestion Flow
- 1. Discover API or create connector
- 2. Confirm discovery → auto-proposes schemas
- 3. Confirm schema → creates entity type
- 4. Propose relationships (if detected) → confirm
- 5. Propose mapping → confirm
- 6. Trigger sync on the connector