🏆 Start Here: Register & Get Aura Credits: Aura Agent Hackathon

Agent Name: GymBuddy :person_lifting_weights:

Live Demo: gymbuddy-gamma-one.vercel.app

GitHub Repo: GitHub - Zor0000/gymbuddy-agent · GitHub

Whenever my actual "pro gym buddy" misses a workout, I’m left staring at taken machines wondering what alternative exercises to do. Since I had just completed my Neo4j Certified Professional certification and the Hackathon was running, I decided to finally solve this problem by building a digital GymBuddy!

What it does: GymBuddy is a graph-native workout and personal training assistant powered by the Neo4j Aura Agent. Instead of generic text generation, GymBuddy uses multi-hop graph reasoning to solve real gym problems.

If a machine is taken, you ask GymBuddy for an alternative. It traverses the graph to find an exercise that targets the exact same primary muscles but uses the equipment you actually have available. It can also build balanced routines, suggest harder/easier progressions, and identify antagonist muscles to keep your training balanced.

Dataset and why a graph fits: I built the knowledge graph using the public domain free-exercise-db (873 exercises).

Fitness is an inherently relational domain, making a graph the absolute perfect fit. Finding an alternative exercise is not a vector-similarity problem (which might return an exercise with the same equipment but wrong muscle); it is a literal two-hop traversal.

My graph schema maps the following Nodes and Relationships:

  • (Exercise)-[:TARGETS {role: 'primary'|'secondary'}]->(Muscle)
  • (Exercise)-[:NEEDS]->(Equipment)
  • (Exercise)-[:PATTERN]->(MovementPattern)
  • (Exercise)-[:PROGRESSES_TO]->(Exercise)
  • (Muscle)-[:ANTAGONIST_OF]->(Muscle)
  • (Muscle)-[:IN_REGION]->(Region)

My graph model explicitly maps: (Original Exercise) -[:TARGETS]-> (Muscle) <-[:TARGETS]- (Alternative Exercise) -[:NEEDS]-> (Equipment). By passing this structure to the Aura Agent via Cypher templates, the LLM’s reasoning becomes 100% deterministic, explainable, and hallucination-free.


:camera_with_flash: Showcase

1. The Aura Agent Configuration Here is how GymBuddy is configured inside the Aura Console, utilizing custom Cypher templates to enforce graph reasoning.

2. Finding Instant Alternatives (Graph Traversal in Action) When the bench is taken, the agent instantly traverses the [:TARGETS] and [:NEEDS] relationships to find a perfect swap.

3. Complex Filtering and Routine Building The agent can filter by muscle region, difficulty level, and equipment simultaneously to build targeted routines.

4. Discovering Progressions Traversing the [:PROGRESSES_TO] relationships allows the agent to scale workouts up or down based on the user's level.


:trophy: Hackathon Reflection

Building directly against the Aura Agent External API was incredibly smooth. By relying on the Aura platform to handle the orchestration and LLM interactions, I was able to focus entirely on building a robust, highly-connected graph model and crafting the exact Cypher templates needed to unlock its value. One small feature request for the future: adding native session memory to the External API (via a sessionId) would be amazing for supporting continuous, multi-turn chats.

LifeGraph: AI Social Resource Navigator

Neo4j Aura Agent Hackathon 2026 - Final Submission


:bullseye: PROBLEM STATEMENT

Millions of people qualify for life-changing assistance but never receive it.

Consider a foster youth aging out of care at 18. She qualifies for 20+ programs that could transform her life:

  • Extended Foster Care (housing + support)
  • Job Corps (training + $500/month stipend)
  • CalFresh (food assistance)
  • Medi-Cal (healthcare)
  • Housing Vouchers (independent housing)
  • And 15+ more programs

But she discovers maybe two.

Why? It's a Graph Problem, Not a Search Problem

Social services are fundamentally interconnected—but presented as isolated silos:

  • Fragmentation: 50+ agencies manage these programs

  • Opacity: Eligibility rules are buried in government documents

  • Hidden Dependencies: She doesn't know that Program A unlocks Program B, which unlocks Program C

  • Missing Context: Traditional search returns: "You might qualify for CalFresh, Job Corps, and housing" — no sequence, no why, no what comes next

The Result: Missed opportunities, prolonged poverty, and human potential left unrealized.

LifeGraph solves this by treating social services as what they really are: an interconnected graph of programs, eligibility, and outcomes.


:light_bulb: VISION

Every person facing a life transition deserves a clear, intelligent path to stability.

Instead of searching blindly through disconnected programs, users see:

  • :white_check_mark: What they qualify for (based on their situation)

  • :white_check_mark: The best sequence to apply (programs unlock each other)

  • :white_check_mark: Where to go (real organizations with contact info)

  • :white_check_mark: What it leads to (concrete outcomes: employment, housing, stability)

Graph reasoning makes this possible.


:rocket: SOLUTION: LifeGraph

A Neo4j knowledge graph of social programs + three specialized AI agents that reason through relationships to guide users to stability.

How It Works

Traditional Search:

"What programs can I get?"
→ Search engine returns list
→ User is overwhelmed
→ User gives up

LifeGraph (Graph-Powered):

"I'm 19, aging out of foster care in Alameda. What's my path?"

↓ GRAPH REASONS:

Extended Foster Care (YOU TRIGGER)
  ↓ UNLOCKS
Transportation Assistance
  ↓ MAKES ACCESSIBLE  
Job Corps Oakland (location, contact, benefits)
  ↓ LEADS TO
Stable employment → Housing secured

Result: Clear 6-month pathway from aging out to financial stability

The difference: Graph reasoning reveals dependencies, sequences, and outcomes that search engines cannot discover.


:bar_chart: WHY GRAPHS ARE NECESSARY FOR THIS PROBLEM

Graph Structure Solves What Relational Databases Cannot

Traditional Database Approach (Relational):

SELECT programs WHERE user_age < 21 AND location = 'Alameda'
→ Returns isolated list: [Extended Foster Care, CalFresh, Job Corps]
→ No understanding of how they connect
→ User still doesn't know the sequence or dependencies

Graph Approach:

MATCH (user:LifeEvent)-[:TRIGGERS]->(p:Program)-[:UNLOCKS]->(p2:Program)-[:LEADS_TO]->(outcome:Outcome)
WHERE user.event = 'AGED_OUT_OF_FOSTER_CARE' AND p.location = 'Alameda'
→ Returns complete journeys
→ Shows implicit dependencies
→ Reveals hidden programs user didn't know existed
→ Explains the "why" and "what comes next"

The Key Insight: Dependencies ARE the Intelligence

In relational databases, relationships are metadata ("this program ID links to this rule ID").

In a knowledge graph, relationships are the intelligence itself:

  • Extended_Foster_Care -[:UNLOCKS]-> Transportation_Assistance (hidden program revealed)
  • AGED_OUT_OF_FOSTER_CARE -[:TRIGGERS]-> Extended_Foster_Care (entry point identified)
  • Job_Corps -[:LEADS_TO]-> EMPLOYED (outcome clarity)

Only a graph can efficiently traverse and reason through these chains.


:building_construction: KNOWLEDGE GRAPH STRUCTURE

Graph Statistics

  • Total Nodes: 127

  • Total Relationships: 246

  • Average Density: 2.5 relationships/node (vs. typical 0.8-1.2)

  • Multi-hop Paths: 100+ unique 3-4 hop sequences

Type Count Examples
Benefit (Programs) 45+ CalFresh, Extended Foster Care, Job Corps, Housing Vouchers, Medi-Cal
Organization 35+ First Place for Youth, Job Corps Oakland, Alameda Workforce Development, YouthBuilt Collective
LifeEvent 12 AGED_OUT_OF_FOSTER_CARE, LOST_JOB, HAD_CHILD, HOMELESSNESS_RISK, DOMESTIC_VIOLENCE
EligibilityRule 20+ Age limits, income caps (<$1,500/month), residency (Bay Area), work requirements
Document 15+ Birth Certificate, ID Card, Proof of Income, Foster Care Documentation
Outcome 10 HOUSING_SECURED, EMPLOYED, FINANCIAL_STABILITY, HEALTHCARE_ACCESS, EDUCATION_COMPLETED

Relationship Types (7 Core Types)

LifeEvent -[:TRIGGERS]-> Benefit
  ↳ When this life event occurs, this program becomes available
  ↳ Example: AGED_OUT_OF_FOSTER_CARE -[:TRIGGERS]-> Extended_Foster_Care
  ↳ Agent use: "Here are programs you can access right now"

Benefit -[:UNLOCKS]-> Benefit
  ↳ Qualifying for one program automatically makes you eligible for another
  ↳ Example: Extended_Foster_Care -[:UNLOCKS]-> Transportation_Assistance
  ↳ Agent use: "This program unlocks three others"

Benefit -[:REQUIRES]-> Document
  ↳ You need this document to apply
  ↳ Example: Foster_Youth_Housing -[:REQUIRES]-> Foster_Care_Documentation
  ↳ Agent use: "Here's what paperwork to gather"

Benefit -[:HAS_RULE]-> EligibilityRule
  ↳ You must meet this condition to qualify
  ↳ Example: CalFresh -[:HAS_RULE]-> (income < $1,500/month)
  ↳ Agent use: "You qualify because your income is under $1,500"

Benefit -[:LEADS_TO]-> Outcome
  ↳ Successfully completing this program leads to this outcome
  ↳ Example: Job_Corps -[:LEADS_TO]-> EMPLOYED
  ↳ Agent use: "This leads to stable employment"

Organization -[:SERVES]-> LifeEvent
  ↳ This organization specializes in helping people in this situation
  ↳ Example: First_Place_for_Youth -[:SERVES]-> AGED_OUT_OF_FOSTER_CARE
  ↳ Agent use: "Organization X helps foster youth"

Organization -[:PROVIDES]-> Benefit
  ↳ This organization delivers this program
  ↳ Example: Job_Corps_Oakland -[:PROVIDES]-> Job_Corps
  ↳ Agent use: "Here's where to go and how to contact them"

Complete Graph Schema

Graph Schema - Complete Node and Relationship Network

Graph Design Principles:

  1. Benefit is the Hub

    • All relationships flow through programs because they're:

      • Triggered by life events (entry point)

      • Unlocking other programs (sequencing)

      • Requiring documents and rules (eligibility)

      • Leading to outcomes (impact)

  2. TRIGGERS + UNLOCKS Create Pathways

     LifeEvent -[:TRIGGERS]-> Program1 -[:UNLOCKS]-> Program2 -[:LEADS_TO]-> Outcome
     = Complete journey from situation to stability
    
  3. Organization Layer Bridges Graph to Reality

    • SERVES and PROVIDES relationships ensure:

      • Finding the right organization for user's situation

      • Getting actual contact info and location

      • Moving from "what to apply" to "where to go"


:robot: THREE SPECIALIZED AURA AGENTS

Agent 1: Eligibility Navigator :clipboard:

Problem it solves: "What programs can I actually qualify for?"

User Example:

"I'm 19, aging out of foster care in Alameda. What programs can I access?"

Agent Response:

  • Lists all programs triggered by user's life event
  • Applies eligibility rules (age, income, residency)
  • Shows required documents
  • Explains why user qualifies
  • Returns actionable next steps

How it works:

  1. Matches (user_event:LifeEvent) -[:TRIGGERS]-> (program:Benefit)
  2. Filters by (program) -[:HAS_RULE]-> (rule) where rule applies to user
  3. Collects (program) -[:REQUIRES]-> (document)
  4. Returns: Programs + Rules + Documents + Explanation


Agent 2: Pathway Advisor :world_map:

Problem it solves: "What's my path to stability? What's the sequence?"

User Example:

"I'm 19 in Alameda, aging out of foster care. I need housing and a job. 
Show me the best pathway to stability."

Agent Response:

  • Builds step-by-step sequences showing program dependencies
  • Explains why each step unlocks the next
  • Shows timeline to outcomes (employment, housing, stability)
  • Reasons through multi-hop relationships

How it works:

  1. Starts with (user_event:LifeEvent) -[:TRIGGERS]-> (p1:Program)
  2. Follows (p1) -[:UNLOCKS]-> (p2) -[:UNLOCKS]-> (p3)
  3. Traces (p_final) -[:LEADS_TO]-> (outcome:Outcome)
  4. Orders programs logically
  5. Returns: Step-by-step plan with "why" explanations

Example Journey:

Step 1: Extended Foster Care
  Why: You aged out of foster care + age < 21 ✓

Step 2: Transportation Assistance (UNLOCKED by Step 1)
  Why: Extended Foster Care automatically includes this
  Impact: Makes Job Corps accessible

Step 3: Job Corps Oakland
  Where: 1801 Embarcadero, Oakland
  Contact: (510) 622-4600
  Benefits: Free training + $500/month stipend
  Why Matters: Transportation enables you to attend

Step 4: Employment (LEADS TO from Job Corps)
  Outcome: Stable monthly income
  Timeline: 6-month training program

Step 5: Independent Housing
  Why Possible: Income from employment enables housing
  Outcome: Financial stability achieved


Agent 3: Resource Locator :round_pushpin:

Problem it solves: "Where can I actually find help?"

User Example:

"Where can I find job training in Alameda County?"

Agent Response:

  • Finds organizations that SERVE user's situation
  • Lists organizations that PROVIDE relevant programs
  • Returns real contact info, locations, eligibility
  • Connects programs to real-world access points

How it works:

  1. Identifies (user_event:LifeEvent)
  2. Finds (org:Organization) -[:SERVES]-> (user_event)
  3. Also finds (org) -[:PROVIDES]-> (program)
  4. Returns: Organization details + Services + Contact + Eligibility

Real Results:

Job Corps Oakland
├─ What: Federal job training & education
├─ Where: Oakland, Alameda County
├─ Contact: (510) 622-4600
├─ Eligibility: Ages 16-24, no income limits
└─ Serves: Individuals seeking employment

Alameda Workforce Development
├─ What: Career services & job training
├─ Where: Alameda, Alameda County
├─ Contact: (510) 832-3500
├─ Eligibility: Free for eligible residents
└─ Serves: Job seekers & displaced workers

YouthBuilt Collective
├─ What: Construction & green jobs training
├─ Where: Alameda County
├─ Contact: (510) 567-9000
├─ Eligibility: Ages 16-29
└─ Serves: Young adults seeking career training


:books: DATA SOURCES

All data is publicly available from official government and nonprofit sources:

Layer 1: Government Programs & Benefits

  1. CA Open Data - CalHHS (https://data.ca.gov/)

    • CalFresh eligibility, WIC rules, Medi-Cal income limits, TANF/CalWORKs
  2. CA Foster Care Indicators Dashboard (https://www.lab.data.ca.gov/)

    • Extended Foster Care age limits, youth transition programs, education support
  3. California Department of Social Services (CDSS) (https://www.cdss.ca.gov/)

    • CalWORKs, TANF, welfare programs, emergency assistance

Layer 2: Community Resources & Organizations

  1. 211.org Database - Alameda County (https://www.211.org/)

    • 50-80+ organizations, services, contact info, eligibility requirements
  2. Alameda County Office of Education (https://www.acoe.org/)

    • Scholarships, youth programs, career pathways
  3. California Foster Care Resources (https://www.fostercare.ca.gov/)

    • Foster youth-focused organizations, education benefits, transition resources

Data Characteristics

  • :white_check_mark: No sensitive personal data — only public program information
  • :white_check_mark: Official sources — government agencies and established nonprofits
  • :white_check_mark: Current — 2024-2025 program documentation
  • :white_check_mark: Regional focus — Bay Area/Alameda County with statewide programs
  • :white_check_mark: Validated — cross-referenced across multiple official sources

:bullseye: HOW JUDGES CAN TEST

Option 1: Test in Aura Console (Live Agents)

Step 1: Access Agents

  1. Open Neo4j Aura Console

  2. Navigate to "Data Services → Agents"

  3. Select the three LifeGraph agents

Step 2: Test Eligibility Navigator

Ask: "I'm 19, aging out of foster care in Alameda. What can I get?"

See:
- List of eligible programs
- Why user qualifies for each
- Required documents
- Next steps

Aura Agent UI

Step 3: Test Pathway Advisor

Ask: "Show me the path to stability. I need housing and a job."

See:
- Step-by-step sequence
- How programs unlock each other
- Why each step matters
- Outcomes (employment, housing, stability)

Step 4: Test Resource Locator

Ask: "Where's job training in Alameda County?"

See:
- Real organizations (Job Corps, Alameda Workforce, YouthBuilt)
- Contact info and locations
- What services they provide
- Eligibility requirements

Step 5: View Reasoning Traces

  • Open agent reasoning panel
  • See agents explicitly acknowledge graph structure
  • Watch them traverse relationship chains
  • See multi-hop pathways being constructed

Option 2: Test Web Application

go to git repo : GitHub - kirthistaank/LifeGraph · GitHub

Setup & Run (See README.md for detailed instructions):

  1. Navigate to the LifeGraph project directory

  2. Install dependencies: pip install -r requirements.txt

  3. Configure environment variables (see STREAMLIT_SETUP_GUIDE.md):

    • ELIGIBILITY_AGENT_ENDPOINT

    • PATHWAY_AGENT_ENDPOINT

    • RESOURCE_AGENT_ENDPOINT

    • NEO4J_API_KEY

    • NEO4J_API_SECRET

  4. Run the app: streamlit run streamlit_app.py

  5. Open browser to http://localhost:8501

Interact with the Application:

  1. Select an agent (Eligibility Navigator, Pathway Advisor, or Resource Locator) in the sidebar
  2. Fill your profile (age, county, situation/goals) using the guided inputs
  3. Review the auto-generated question pre-populated in the main prompt area
  4. Ask your question - Edit the initial question or ask as-is
  5. See real-time response with graph reasoning
  6. Ask follow-up questions - The agent remembers your conversation context
  7. View reasoning traces - Expand "View graph reasoning" to see how the agent traversed the knowledge graph

:counterclockwise_arrows_button: WHY NEO4J AURA MADE THIS SMOOTH

Challenge: Multi-Hop Reasoning at Scale

Without Neo4j Aura:

  • SQL queries would require complex JOINs (5-7 tables minimum)
  • Impossible to efficiently explore unknown paths ("find all programs that lead to employment")
  • Poor performance with relationship traversal

With Neo4j Aura:

MATCH (event:LifeEvent)-[:TRIGGERS]->(p1:Program)
      -[:UNLOCKS]->(p2:Program)-[:LEADS_TO]->(outcome:Outcome)
WHERE event.name = 'AGED_OUT_OF_FOSTER_CARE' 
  AND p1.location = 'Alameda'
RETURN p1, p2, outcome

Result: Complex multi-hop reasoning in milliseconds.

Why Aura Specifically

  1. Managed Infrastructure

    • No DevOps overhead

    • Automatic scaling

    • Built-in security and backups

  2. Agents Integration

    • Neo4j Aura Agent framework is purpose-built for knowledge graphs

    • Agents can reason through relationships natively

    • Text2Cypher automatically converts questions to graph queries

  3. Relationship Reasoning

    • Aura excels at what other databases struggle with: traversing relationships

    • Each relationship is indexed and optimized

    • Multi-hop queries scale linearly, not exponentially

  4. Cost-Effective

    • Free tier sufficient for hackathon demo

    • ~$0.35/hour for external agent access (minimal)

    • No database redesign needed for scaling


:globe_with_meridians: WEB APP INTEGRATION: Easy + Elegant

Architecture: Graph + Agents + Streamlit

┌─────────────────────────────────────────┐
│         Streamlit Web App               │
│  ┌─────────────────────────────────────┤
│  │  Chat Interface                     │
│  │  - Select Agent                     │
│  │  - Fill Profile                     │
│  │  - Ask Question                     │
│  └─────────────────────────────────────┤
└────────────────┬────────────────────────┘
                 │
                 ↓ (REST API)
┌─────────────────────────────────────────┐
│    Neo4j Aura Agent (External)          │
│  ┌─────────────────────────────────────┤
│  │  Text2Cypher                        │
│  │  ↓ converts question to query       │
│  │  Cypher Template                    │
│  │  ↓ executes on graph                │
│  └─────────────────────────────────────┤
└────────────────┬────────────────────────┘
                 │
                 ↓
┌─────────────────────────────────────────┐
│    Neo4j Aura Database                  │
│  ┌─────────────────────────────────────┤
│  │  Knowledge Graph                    │
│  │  - 127 nodes (programs, orgs, etc)  │
│  │  - 246 relationships                │
│  │  - Multi-hop paths optimized        │
│  └─────────────────────────────────────┤
└─────────────────────────────────────────┘

Why Integration Was Seamless

  1. REST API First

    • Aura agents expose REST endpoints

    • Streamlit just needs to POST questions

    • Get JSON responses back

  2. Authentication Simple

    • Neo4j API credentials (not database credentials)

    • Standard OAuth token exchange

    • Works with any web framework

  3. Stateless Design

    • Each question is independent

    • No session management needed

    • Agents handle all reasoning

  4. Rapid Development

    • No custom agent logic needed

    • Aura agents work out-of-the-box

    • Focus on UX, not backend plumbing

Code Example: Calling Agent from Streamlit

def call_agent(agent_name: str, question: str) -> dict:
    """Call a Neo4j Aura Agent via REST API"""
    
    # Get bearer token (simple OAuth exchange)
    token = get_bearer_token(api_key, api_secret)
    
    # Call agent endpoint
    response = requests.post(
        agent_endpoint,
        headers={
            "Authorization": f"Bearer {token}",
            "Content-Type": "application/json"
        },
        json={"input": question},
        timeout=60
    )
    
    # Return parsed response
    return response.json()

That's it. No database connection, no query building, no response parsing.



:trophy: WHAT DIFFERENTIATES LIFEGRAPH

vs. Traditional Benefits Directory

Traditional: Search → List of programs → User confused → User gives up
LifeGraph: Ask question → Get sequenced plan → User empowered → User acts

vs. Search Engine

Search: "What programs can I get?" → Irrelevant results
LifeGraph: Same question → Relationship reasoning → Relevant, sequenced, complete

vs. Linear Rule Engine

Rule Engine: "If age < 21 THEN extend foster care" (one condition)
LifeGraph: "Extend foster care TRIGGERS transportation assistance UNLOCKS job corps LEADS_TO employment"
         (complete chain, revealing hidden dependencies)

Unique Value Propositions

  1. Dependency Navigation

    • First to focus on "what unlocks what"

    • Not just listing programs, but explaining sequences

  2. Multi-Hop Reasoning

    • Connects 3-4 program hops in seconds

    • Reveals outcomes (housing, employment, stability)

  3. Real Data, Real Impact

    • Based on actual CA social services

    • Real organizations, real phone numbers, real eligibility rules

  4. Graph-Powered Intelligence

    • Only possible with Neo4j's relationship traversal

    • Can't be replicated with traditional databases or simple search

  5. Transparency

    • Every recommendation includes reasoning

    • Users understand why they qualify

    • Builds trust


:chart_increasing: IMPACT

For Foster Youth

  • Clear path from aging out → employment → independence

  • Access to interconnected support system

  • Transparent reasoning (understanding why programs matter)

For Government

  • Reduced duplicated effort (agencies know who's applying where)

  • Better outcomes tracking (see which programs lead to employment)

  • Smarter resource allocation


LifeGraph: Because foster youth deserve a clear path to stability. :rocket:

Built with Neo4j Aura. Powered by graph reasoning. Made for people.

Beyond the Org Chart: Decoding the Organizational Matrix with NeoSmith

"Welcome to the real data, Neo. You’ve been looking for a different way to lead, haven’t you? I am here to show you the truth of your organization."

Agent Name: NeoSmith

Check our live demo video in HERE

What it does

NeoSmith is an enterprise-grade AI Organizational Intelligence Agent that serves as a Digital Twin co-pilot for executive leadership. It fuses two distinct cognitive layers to navigate the "matrix" of your company:

  • The Agent Smith Layer:Implements systemic awareness, treating the company as a unified grid of nodes and dependencies to map silos and bottlenecks.
  • The Neo Layer:Focuses on human-centric optimization, engineering cross-departmental collaboration and dynamic "human circularity" to repurpose talent dynamically.

It is not just a chatbot, it is a GraphRAG system that uses specialized tools like Parameterized Cypher Templates and Vector Similarity Search to provide safe, deterministic, and highly intelligent organizational insights.

Dataset and why a graph fits

We utilize a synthetic dataset of 5,000 active employees and 500 open positions, modeled across 10 departments with over 16,000 relational edges.

A graph database is the only architecture capable of handling the multidimensional truth of an enterprise:

  • ONA (Organizational Network Analysis):Traditional relational databases fail to capture informal collaboration pathways—the "hidden network" that actually drives your business.
  • Talent Circularity:We use skill adjacencies to calculate training timelines, moving talent between departments in real-time, preventing the "blind headcount cuts" of traditional HCM software.
  • Path Dependency:Only a graph can perform multi-hop shortest-path calculations in milliseconds to expose how information—or friction—flows across your entire grid.

Showcasing the Power of NeoSmith

  1. Human Circularity: We turn layoffs into mobility. The agent matches redundant assets to new roles globally, calculating the exact reskilling path in seconds.

Question: “Execute a targeted talent mobility routing analysis specifically for Jake Peralta. Map his skills against global open positions and check if there are placements available that require reskilling weeks.”

  1. Quiet Forces Mapping:We identify the informal leaders, the ones who hold the culture together, beyond the official hierarchy.

Question: " Identify the top 5 grassroots informal network influencers who operate strictly as individual contributors. Look at the role level property and exclude any nodes where the level is 'Manager', 'Director', or 'C-Level'. They must have high influence scores and actively collaborate across multiple departments."

Question: “We have open positions requiring Python skills. Who are the highly proficient, high-influence Python experts inside the company who could act as upskilling mentors for internal transfers?”

  1. Flight Risk Mitigation: We simulate departures to proactively detect structural silos and bridge the knowledge gap before it impacts the bottom line.

Question: “If Wanda Swanson leaves the company, perform a structural safety analysis. Execute the reallocation tool and ensure you pass an empty string for the source scope parameter.Find high-priority open positions company-wide. ”

Instead of firing, relocate! !! :grin:

Why this build matters

NeoSmith doesn’t just return a list, it shows the "code" of the organization, the structural silos, the quiet for ces and the hidden mentors.

“All I’m offering is the truth. What would you like to explore?”

View the full NeoSmith repository and Demo Logs on Git: Link

Mental Health Assistant

The Mental Health Assistant is a knowledge graph agent that reasons over a curated psychology and mental health dataset. It can answer clinical questions about disorders, symptoms, therapies, medications, neurotransmitters, and lifestyle risk/protective factors — and explain the connections between them.

Example questions it handles:

  • "What are the best treatments for Post-Traumatic Stress Disorder?"
  • "Which disorders are commonly comorbid with Major Depressive Disorder?"
  • "What medications treat Bipolar Disorder I and are they FDA approved?"
  • "What life factors influence Major Depressive Disorder?"
  • "How does Sertraline work at a neurotransmitter level?"

Dataset and why a graph fits

The dataset was purpose-built for this hackathon covering 15 mental health disorders, 25 symptoms, 13 therapies, 14 medications, 5 neurotransmitters, and 10 lifestyle factors — with over 150 relationships between them.

A graph is the natural fit because mental health is fundamentally relational. A disorder doesn't exist in isolation — it shares symptoms with other disorders, responds to multiple therapies, is treated by medications that modulate specific neurotransmitters, and is influenced by lifestyle factors. These multi-hop relationships are exactly what graph databases excel at and what makes the agent's reasoning genuinely useful.

Relationships used:
(Disorder)-[:HAS_SYMPTOM {frequency, severity}]->(Symptom)
(Disorder)-[:TREATED_BY {efficacy_score, line}]->(Therapy)
(Disorder)-[:TREATED_WITH {line, fda_approved}]->(Medication)
(Disorder)-[:OFTEN_COMORBID_WITH {comorbidity_rate}]->(Disorder)
(Medication)-[:MODULATES {action}]->(Neurotransmitter)
(LifeFactor)-[:INFLUENCES {effect_size}]->(Disorder)

Tools used

  • Cypher Templates — for structured queries (treatments, symptoms, comorbidities, medications, life factors, neurotransmitter mechanisms)
  • Text2Cypher — for open-ended natural language questions

Note: full disorder names required (abbreviation support is a planned improvement)

Known limitations / future improvements

  • Abbreviations like PTSD, MDD, GAD not yet supported — use full disorder names
  • Similarity search (vector embeddings) not yet implemented
  • Dataset could be expanded with more disorders and real-world prevalence data

Agent Tools:


Use of reasoning and thought:

Clean Response:

Agent Name: TabletopGameRecommender

What it does: The TableTopGame Recommender analyses my personal board game collection by treating it as a highly interconnected network of games, mechanics, designers, and themes. It delivers instant, personalised game recommendations based on scenarios given.

Dataset and why a graph fits: Used dataset is a collection of my personal collection of 200 tabletop games with their corresponding game information scraped from BoardGameGeek (BGG).

A graph database is fit for the tabletop game recommender because board games are naturally connected by complex, multi-layered relationships rather than isolated rows.

The scraped BGG data is modeled as a Graph consisting of distinct node types and the connections between them.

Node Types (Entities)

  • Game: The core entity (e.g., Catan, Gloomhaven, Ark Nova). Contains properties like name, weight (complexity), year, min/max players, and playtime.
  • Designer: The creator of the game (e.g., Jamey Stegmaier, Uwe Rosenberg).
  • Artist: The visual creator (e.g., Ian O'Toole).
  • Publisher: The company that released it (e.g., Stonemaier Games).
  • Mechanic: The core gameplay systems (e.g., Worker Placement, Deckbuilding, Drafting).
  • Category: The thematic genre (e.g., Sci-Fi, Economic, Fantasy).
  • Family: BGG groupings (e.g., Solitaire Games, Crowdfunding: Kickstarter). [1]

Relationship Types (Edges)

  • (:Game)-[:DESIGNED_BY]->(:Designer)
  • (:Game)-[:HAS_MECHANIC]->(:Mechanic)
  • (:Game)-[:BELONGS_TO]->(:Category)
  • (:Game)-[:PUBLISHED_BY]->(:Publisher)

Screenshot of your agent in the Aura console:

Screenshot or short demo of your agent in action:

====================

Scenario: I am hosting a large group of 8 players for a game night, but we only have about 25mins of available play time

====================

Scenario: I am hosting a game night with three friends who wanted a deep strategy game.
After the agent recommended a list of strategic game titles, we narrowed our focus and updated the criteria to specify a preference for deck building mechanics.

====================

Scenario: Specify that I am a fan of certain game publisher and wanted strategy games for 4 persons but with no preference for the game play time and complexity

Jibarito Agent - Neo4j Aura Agents Hackathon Submission

Agent Name

Jibarito — Puerto Rican farmer/campesino
An agricultural intelligence agent for the US Caribbean & tropical regions


What It Does

Jibarito is a bilingual (Spanish/English) AI agent powered by Neo4j AuraDB that helps farmers, gardeners, agronomists, and researchers make data-driven agricultural decisions.

Aura Console Screenshots



:clapper_board: Live Demo

YouTube Demo Video: https://youtu.be/22F9bWTdzvs

Features demonstrated:

  • Real-time queries in English and Spanish
  • Companion planting recommendations
  • Production statistics & comparisons
  • Dark mode UI with Jibarito branding
  • Data attribution to USDA, CrophGraph & Neo4j

:globe_with_meridians: Live Application

Try Jibarito: https://jibarito.streamlit.app/

  • Click example questions in the sidebar
  • Type your own questions (English or Spanish)
  • Get instant agricultural intelligence
  • All responses powered by Neo4j AuraDB

Answers questions about:

  • Crop Production Statistics — What's grown where, historical trends (USDA NASS data)
  • Companion Planting — What plants grow well together with mechanisms & sources
  • Pest & Disease Management — Organic solutions for agricultural pests
  • Growing Information — Spacing, harvest times, climate requirements
  • Regional Comparison — Compare production across 4 territories
  • Bilingual — Ask in English or Spanish, get answers in your language

Dataset & Why a Graph Fits

The Data

  • 92,218 Agricultural Production Records from USDA NASS Quick Stats
  • 4 US Territories: Puerto Rico, US Virgin Islands, Hawaii, Florida
  • 3 Census Years: 2018, 2022, 2023
  • 228 Crops
  • 262 Pests

Why Neo4j Graph is Perfect

Agricultural intelligence is fundamentally about relationships, not isolated data:

  1. Companion Planting Networks → "What grows well WITH tomatoes?"
  2. Crop Rotation Sequences → "What to plant AFTER tomatoes?"
  3. Pest Management Relationships → "What pests attack tomatoes?"
  4. Production Context → Commodity → AgRecord → Geography → County with full history
  5. Semantic Discovery → Vector similarity on 92K production records

Final Graph Statistics

  • 92K+ Nodes — territories, counties, commodities, plants, pests, operations
  • 213K+ Relationships — production, companions, pests, rotations, geography
  • Vector Index on 92,218 AgRecords (OpenAI embeddings, cosine similarity)

Graph Schema

Layer 1: Production Statistics

Source: USDA NASS Quick Stats

ClimateZone → Geography → County

AgRecord ──→ IS_COMMODITY  ──→ Commodity ──→ THRIVES_IN ──→ ClimateZone
         ──→ FOR_GEOGRAPHY ──→ Geography
         ──→ REPORTED_IN   ──→ County

CommodityGroup ──→ HAS_COMMODITY ──→ Commodity

OperationStats ──→ STATS_FOR ──→ Geography | County

Layer 2: Horticultural Intelligence

Source: CropGraph API + USDA PLANTS Database

Plant ──→ COMPANION_OF    ──→ Plant          (mechanism, strength)
      ──→ ANTAGONIST_OF   ──→ Plant         
      ──→ HAS_PEST         ──→ Pest           (severity, type)
      ──→ BELONGS_TO_FAMILY ─→ RotationFamily
      ──→ SAME_AS          ─→ Commodity      (bridge to Layer 1)

RotationFamily ──→ ROTATE_TO ──→ RotationFamily

:file_cabinet: Technology Stack

Component Technology
Graph Database Neo4j AuraDB
Agent Platform Neo4j Aura Agent
Embeddings OpenAI text-embedding-3-small (1536 dims)
Frontend Streamlit 1.31.0
Deployment Streamlit Cloud

:chart_increasing: Data Sources

Source Type License Records
USDA NASS Quick Stats Production statistics CC0 92,218
USDA Census Farm operations CC0 Operations data
CropGraph API Companion planting, pests, spacing Open 91 crops
USDA PLANTS Botanical traits Public Domain 125 crops

:bullseye: Example Queries

English:

  • "How many tomatoes were grown in Puerto Rico in 2022?"
  • "What should I plant next to tomatoes?"
  • "What pests attack peppers?"
  • "What crops are grown in Hawaii?"

Spanish:

  • "¿Cuántos tomates se produjeron en Puerto Rico en 2022?"
  • "¿Qué debo sembrar junto a los tomates?"
  • "¿Qué plagas atacan los plátanos?"
  • "¿Qué cultivos se cultivan en Hawái?"

:building_construction: Architecture

User Query (Streamlit)
    ↓
OAuth2 Token Generation (Neo4j)
    ↓
REST API → Neo4j Aura Agent
    ↓
Agent Tools:
  • Similarity Search (vector embeddings)
  • Commodity Queries (Cypher templates)
  • Companion Plant Relationships
  • Pest Management Info
  • Growing Characteristics
    ↓
Neo4j AuraDB
  • 92K+ nodes
  • 213K+ relationships
  • Vector index (ag_embeddings)
    ↓
Clean Response → User


:graduation_cap: Key Decisions

Scope Selection

  • 4 territories + 3 census years fitting AuraDB limits

Multi-Layer Design

  • Layer 1 (Production Stats) — USDA NASS data for exact queries
  • Layer 2 (Horticultural Intelligence) — CropGraph + USDA PLANTS for recommendations
  • Separation enables both precise queries and discovery-based learning

Bilingual Support

  • Puerto Rico + Spanish-speaking farmers require native Spanish support
  • Aura Agent naturally handles language switching via system prompt

Vector Embeddings

  • OpenAI text-embedding-3-small (1536 dims) chosen to match Aura Agent's default
  • Enables semantic similarity search and agricultural records

:rocket: How to Use Jibarito

  1. Visit: https://jibarito.streamlit.app/
  2. Choose: Click any example question in sidebar OR type your own
  3. Wait: Agent processes your question using Neo4j knowledge graph
  4. Learn: Get data-driven agricultural intelligence in your language

:link: Links

  • GitHub Repo: https://github.com/acarrasquillo/jibarito_agent

Built for the Neo4j Aura Agents Hackathon | June 2026

OSS Sentinel: Mapping Human Risk in Open Source Dependencies

What It Does

OSS Sentinel is a graph-powered AI agent that helps developers identify sustainability risks hidden inside their software supply chain.

Instead of focusing on known vulnerabilities, OSS Sentinel analyzes the people behind open-source packages. It identifies packages with low bus factors, inactive maintainers, growing issue backlogs, and weak project health signals that could become future points of failure.

Users upload dependency files such as package.json, requirements.txt, go.mod, or Cargo.toml. The system builds a knowledge graph connecting packages, repositories, contributors, and dependency relationships, then exposes the graph through a Neo4j Aura Agent for natural-language investigation.

The Problem

Incidents like Log4Shell and the xz-utils backdoor revealed that critical infrastructure often depends on projects maintained by a handful of volunteers.

Traditional dependency scanners answer:

Is this package vulnerable?

OSS Sentinel answers:

Is this package sustainable?

A package with millions of weekly downloads and a single inactive maintainer may represent a serious organizational risk long before a CVE appears.

Why Neo4j

This is fundamentally a graph problem.

Questions such as:

  • Which dependencies in my project have only one active maintainer?
  • What is the riskiest package in my dependency tree?
  • Which critical packages haven't seen commits in the last year?
  • How many hops away is a high-risk dependency?

require traversing relationships across packages, repositories, contributors, and transitive dependencies.

Neo4j enables these relationships to be modeled and queried naturally, while Aura Agent allows users to explore the graph using plain English.

Architecture

User Upload
    │
    ▼
Dependency Parser
    │
    ▼
External Data Collection
 ├─ deps.dev
 ├─ GitHub API
 └─ npm / PyPI Statistics
    │
    ▼
Risk Scoring Engine
    │
    ▼
Neo4j AuraDB
 ├─ Package
 ├─ Repository
 ├─ Contributor
 └─ Scan
    │
    ▼
Neo4j Aura Agent
    │
    ▼
Natural Language Risk Analysis

Graph Model

The graph contains:

  • Package
  • Repository
  • Contributor
  • Scan

Relationships:

  • DEPENDS_ON
  • HOSTED_AT
  • MAINTAINED_BY
  • INCLUDES

This structure allows dependency risk to be traced all the way from an application to the maintainers responsible for each package.

Risk Model

Each package receives a composite risk score based on:

  • Bus Factor
  • Maintainer Inactivity
  • Open Issues
  • OpenSSF Scorecard Health

Packages are categorized as:

  • HIGH
  • MEDIUM
  • LOW

This makes it easy to identify critical dependencies requiring attention.

Aura Agent in Action

OSS Sentinel uses Neo4j Aura Agent as the primary interface for investigating dependency risk.

Instead of writing Cypher queries, developers can ask natural-language questions about their dependency graph.

Example questions include:

  • Which package is riskiest?
  • Find packages with bus factor 1.
  • Are there dependencies with no commits in the last 12 months?
  • Which dependency is a single point of failure?
  • Show me risky packages in my dependency tree.

The Aura Agent translates these questions into graph operations and returns actionable insights backed by live dependency and maintainer data.

This allows developers to move from raw graph exploration to conversational risk analysis while still leveraging Neo4j's graph traversal capabilities underneath.

Screenshots

Aura Agent Configuration

Screenshot showing the Aura Agent running inside Neo4j Aura Console.

OSS Sentinel Dashboard

The dashboard visualizes overall package health, risk distribution, and dependency sustainability metrics.

Neo4j Knowledge Graph

Graph visualization showing packages, repositories, contributors, and dependency relationships stored in AuraDB.

Tech Stack

  • Neo4j AuraDB
  • Neo4j Aura Agent
  • FastAPI
  • MongoDB Atlas
  • Next.js 16
  • TypeScript
  • Tailwind CSS
  • GitHub API
  • deps.dev
  • npm Registry
  • PyPI Statistics

What Makes This Different

Most software supply-chain tools focus on security vulnerabilities.

OSS Sentinel focuses on sustainability vulnerabilities.

By mapping dependency trees to the people maintaining them, OSS Sentinel helps teams identify succession risk, maintainer burnout, and critical single points of failure before they become security incidents.

Try it out: GitHub - isthatananya/packages-intel · GitHub

:trophy: Agent Name

Sybil-Hunter: E-Commerce Review Fraud Network Agent

:laptop: What it does

Sybil-Hunter is an intelligent AI agent built to uncover astroturfing, coordinated fake review rings, and Sybil attacks on e-commerce platforms. While traditional relational databases or flat dashboards can easily flag an isolated 5-star or 1-star review, they fail to see structural collusion where networks of fake accounts coordinate to manipulate product ratings.

Using multi-hop graph reasoning, Sybil-Hunter crawls connection paths to find groups of distinct user accounts that consistently review the exact same products within narrow time frames. The agent acts as an automated investigator: users can ask natural language questions like "Check whether this user is a sybil" and the agent translates this directly into a structural graph traversal, surfacing hidden fraud rings instantly.

:bar_chart: Dataset and why a graph fits

  • Dataset: A dense, highly connected subset of the Amazon Fine Food Reviews dataset from Kaggle, containing user profiles, unique product IDs, ratings, timestamps, and review data.

  • Why a graph fits: Fraud is fundamentally a structural problem, not an isolated data point. In a relational database, finding a ring of X users who colluded to review the same 5 products requires massive, multi-way self-joins and sub-queries that could break at scale.

In Neo4j, this is a clean, natural traversal. By structuring the data as: (:User)-[:POST]->(:Review)-[:ABOUT]->(:Product)

The agent can use graph topology to look for closed loops and tightly knit clusters (e.g., matching common paths where User A and User B share multiple Product leaf nodes). A graph doesn't just calculate a statistical correlation; it provides an explicit, audit-ready chain of relationships explaining exactly why a group of accounts is flagged as a coordinated Sybil network.

:camera_with_flash: Screenshot of your agent in the Aura console

:movie_camera: Screenshot or short demo of your agent in action

:link: Optional: link to your agent if available

https://api.neo4j.io/v2beta1/organizations/3bb9b4f1-7f16-43d9-9046-8ab0da25ae5d/projects/3bb9b4f1-7f16-43d9-9046-8ab0da25ae5d/agents/7efe4d1b-ccd5-4d2c-bfb1-dd40d25f9dbd/invoke

ANIP: Athlete Nutrition Intelligence Platform for FIFA World Cup 2026

Agent Submitted:
Three Neo4j Aura Agents: DietaryComplianceAgent, StakeholderCommsAgent, and AnalyticsAgent orchestrated by two LangGraph agents (InjuryResponseAgent, NutritionAgent) over a Knowledge Graph of 1,400+ athletes, 48 teams, 16 venues, 125+ ingredients across 39 tournament days.

What It Does:
When an injury is logged, this solution ANIP runs an 11-step chain producing:
(a) a new nutrition phase + macro targets,
(b) a 3-day recovery meal plan citing past validated precedents,
(c) a graph-grounded compliance verdict per ingredient, and
(d) a persona- and language-aware notification to the team nutritionist.

The design and architecture transfers directly to the Olympics, Rugby World Cup, F1 paddock catering, and other major sporting events where nutrition is operationally critical and culturally complex.

Dataset & Why a Graph Fits:
Imagine the World Cup kitchen as a web, this athlete is vegetarian, so every animal-derived ingredient must be excluded; that exclusion applies to this entire ingredient category; that category maps to dozens of dishes across this venue; this venue cooks for three teams tonight. A relational schema would scatter these facts across tables and join them at query time. A graph stores the relationships natively. Asking "is this meal plan safe for this athlete?" becomes one traversal rather than a multi-table join.

The graph contains ~9 primary node labels and ~14 relationship types. The Aura Agents use a mix of fixed Cypher templates (for safety-critical compliance checks where determinism matters) and Text2Cypher tools (for exploratory KPI queries) against the same live AuraDB instance.

Node label Properties (selected) Key relationships
Athlete id, name, position, weight_kg, height_cm, dob, squad_number PLAYS_FOR→Team, HAS_PROFILE→NutritionProfile, HAS_RESTRICTION→DietaryRestriction, HAS_INJURY→InjuryRecord
Team fifa_code, country, group, halal_pct PLAYS_AT→Venue
NutritionProfile phase, kcal_target, protein_g, carb_g, fat_g, hydration_ml, last_updated (child of Athlete)
DietaryRestriction type (halal/vegan/kosher/gluten_free/allergy), subtype, is_religious, is_medical (linked from Athlete)
Ingredient id (ING-NNN), name, category, is_halal, is_vegan, is_kosher, allergens SUPPLIED_BY→Vendor, COMPLIES_WITH→DietaryRestriction
InventoryItem ingredient_id, quantity, unit, safety_threshold STORED_AT→Venue
Vendor name, region, lead_time_days, halal_certified, primary (linked from Ingredient)
DecisionTrace id, agent_id, decision_type, tournament_day, timestamp HAS_SITUATION, HAS_RATIONALE, HAS_ACTION, HAS_OUTCOME, CITES_PRECEDENT, PART_OF_WORKFLOW
Situation/Rationale/Action/Outcome (per-decision child nodes — see Context Graph) (children of DecisionTrace)
Precedent id, similarity_tags, validated_by, reuse_count, decision_trace_id VALIDATED_AS←DecisionTrace, SIMILAR_TO↔Precedent

"Octopus" Brain: Context Graphs - How ANIP Remembers
An octopus has nine brains — one central, eight in its arms. ANIP's Context Graph works the same way: each agent decision grows a new arm of memory that every future agent can reach into.

The Context Graph is the institutional-memory layer that turns stateless LLM calls into a learning system. Every agent decision creates one DecisionTrace node and four child nodes capturing the full reasoning record.

Promotion to precedent: when an outcome is validated by a nutritionist with positive feedback, a Precedent node is created carrying the trace ID plus similarity_tags (e.g. [halal, hamstring, grade2, urgency_36hr, midfielder]). A GDS job computes SIMILAR_TO edges between Precedents using Jaccard similarity over those tags.
Retrieval at inference time: the NutritionAgent's precedent-lookup node fires the query, scored on tag overlap and recency:

Why this matters: the cited precedent is injected directly into the LLM prompt - past situation, past reasoning, past outcome, etc so the model anchors on validated organizational knowledge rather than generating from scratch. By Round of 16 of the tournament, ANIP has accumulated multiple of validated precedents, and reuse_count tracks which decisions consistently work. The Context Graph is also fully auditable: any decision can be replayed in court-admissible form by traversing the DecisionTrace subgraph.


Orchestrator, Messenger, Oracle: Three Agents Walk Into a Graph
LangGraph Agents, A2A Messaging, and Aura Agents - why the concoction? LangGraph owns the workflow. A2A owns the handoff. Aura Agents own the graph-grounded answers. Pull any one out and the system either hallucinates, loses state, or can't audit itself.

  • LangGraph owns workflow orchestration because injury → nutrition requires conditional branching, persistent typed state, and structured Neo4j writes at each node and not just text generation. Each LangGraph node receives the full AgentState (TypedDict) plus the Neo4j driver/MCP, allowing it to read context and MERGE nodes/relationships in one transaction.

  • A2A (Agent-to-Agent) messaging is the contract between LangGraph Agents and Aura Agents. When InjuryResponseAgent finishes, it emits a typed payload: { athlete_id, injury_record_id, decision_trace_id, new_macros, restrictions, urgency } which NutritionAgent picks up and uses to load the full graph context.

  • Aura Agents are then called with the trace_id as the anchor, so every downstream answer is grounded in a verifiable graph node, not floating LLM output. Aura Agents are deployed in the Aura console with OAuth 2.0 token auth. Each combines a system prompt, fixed Cypher templates (deterministic), and Text2Cypher tools (flexible). DietaryComplianceAgent's safety-critical Cypher template:

    [Dia 2 in doc]


Agent Pipeline

# Step · Agent Layer Action
1 Receive Injury · InjuryResponseAgent LangGraph Reads athlete profile, restrictions, current phase via Cypher MATCH on Athlete-PLAYS_FOR-Team.
2 Classify Injury · InjuryResponseAgent LangGraph LLM classifies type/severity/urgency; decides phase change.
3 Macro Targets · InjuryResponseAgent LangGraph Computes kcal/protein/carb/fat per phase, applies restriction constraints.
4 Write Graph · InjuryResponseAgent LangGraph MERGEs InjuryRecord, WorkflowSession, DecisionTrace (Situation/Rationale/Action).
5 A2A Message · InjuryResponseAgent LangGraph Emits payload {athlete_id, trace_id, macros, restrictions} to NutritionAgent.
6 Receive A2A · NutritionAgent LangGraph Loads athlete + injury context from graph using trace_id.
7 Precedent Lookup · NutritionAgent LangGraph Traverses SIMILAR_TO from current Situation to past Precedent nodes.
8 Meal Plan · NutritionAgent LangGraph LLM generates 3-day plan using ING-NNN codes, conditioned on cited precedent.
9 Compliance Check · DietaryComplianceAgent Aura Agent Cypher template walks Ingredient → is_halal/is_vegan/allergen flags against athlete restriction.
10 Write Trace · NutritionAgent LangGraph MERGEs NutritionAgent DecisionTrace, CITES_PRECEDENT, links to InjuryRecord.
11 Compose Alert · StakeholderCommsAgent Aura Agent Reads DecisionTrace via apoc.convert.fromJsonMap, composes persona/language-routed message.

Executing a scenario on ANIP

Scenario 1:Player is injured, dietary ingredient stock level is critically low



Demo Video: https://youtu.be/wWpEfW_qTYI



Scenario 2:Player is injured is vegan. Need to check diet ingredients

(Explained in document video. Link below)


Neo4j Aura Agents


DietaryComplianceAgent

[Dia 3 in document video. Link below]


StakeholderCommsAgent

[Dia 4 in document video. Link below]


AnalyticsAgent

[Dia 5 in document video. Link below]


Closing Thoughts

Neo4j Aura Agents transformed three Cypher queries into three intelligent, graph-grounded decision-makers: compliance, communication, and analytics. Each one impossible to hallucinate because the answer lives in the graph, not the model.

Next on the roadmap are SupplyChainAgent and KitchenOpsAgent, closing the loop from injury to plate entirely within Aura Agents.

Thank you to Neo4j for building the platform that made this possible and for the opportunity to push its boundaries at solving complex enterprise problems.


document video: https://youtu.be/tvpRmCrwjK0

(document video was created as I can only post 4 screenshots. Also I can post only 2 links)

MovieGraph Agent

Agent Name: MovieGraph Agent

What it does:
MovieGraph Agent answers simple questions about movies by exploring relationships between actors, movies, and genres stored in Neo4j Aura.

Dataset and why a graph fits:
The dataset contains movies, actors, and genres connected through relationships such as ACTED_IN and IN_GENRE. A graph database is a natural fit because movies and people are highly interconnected, making it easy to explore and understand these relationships.

Tools Used:
Cypher Queries

Example Queries:

  1. Find movies acted in by Leonardo DiCaprio.
  2. Find movies belonging to a specific genre.

Screenshots:
• Aura graph visualization showing nodes and relationships.
• Query results demonstrating the agent in action.

Built using Neo4j Aura Free.

Aura Agent Hackathon Submission

Thread title: GraphImmune Trust Agent


Agent Name

GraphImmune Trust Agent

What it does

GraphImmune is a trust layer for knowledge graphs, it audits a graph before an AI/RAG system relies on it. You ask one plain question . "Is this graph safe for RAG?" and the agent reasons over a live Neo4j Aura graph, deciding which tools to run.

It finds the defects that quietly break RAG:

  • Contradictions : the same subject→object asserted two opposite ways (a trusted source says "RAG reduces hallucination", a stale low-trust source says "RAG increases hallucination").
  • Duplicate entities (Celiac vs Coeliac Disease), unsupported claims (no evidence), weak relations, orphan and stale claims.

For every issue it explains why it matters using the graph's own evidence, the claim, its evidence sentence, the source document and that source's reliability then returns a Knowledge Health Score and a GraphRAG Readiness rating, and proposes safe, auditable Cypher repairs (ALIAS_OF, DISPUTED_WITH) that link and flag without ever deleting the original knowledge.

Tools (all three Aura tool types):

  • Cypher Template - find_contradictions (claims about one subject/object with opposing relations) and claims_by_issue (claims carrying a detected trust issue).
  • Text2Cypher - turns ad-hoc questions ("how many claims are below 0.6 confidence?") into read-only Cypher.
  • Similarity Search - fuzzy/full-text retrieval of related claims — the "what would a RAG retriever surface?" view.

It doesn't just answer - it tells you whether the knowledge is trustworthy in the first place, and shows its work.

Dataset and why a graph fits

The dataset is a document-derived trust corpus: source documents tagged by reliability (trusted / unknown / low-trust), broken into evidence-backed claims, deliberately seeded with real contradictions, duplicates, stale facts and unsupported claims.

A graph fits because trust is relational and multi-hop, not tabular:

  • A contradiction is literally two paths from the same subject to the same object with opposing relations, trivial in Cypher, painful in SQL.
  • Every claim traces to its evidence and source: Evidence -[:SUPPORTS]-> Claim, Document -[:HAS_CHUNK]->...-> Evidence.
  • Duplicates/orphans fall out of name similarity and node degree.
  • Every repair is preserved as an auditable edge, so trust decisions stay explainable.
Document -[:HAS_CHUNK]-> Chunk -[:CONTAINS]-> Evidence -[:SUPPORTS]-> Claim
Entity   -[:IS_SUBJECT_OF]-> Claim -[:HAS_OBJECT]-> Entity
Claim    -[:HAS_ISSUE]-> Issue -[:SUGGESTS]-> Repair

Screenshot — agent in the Aura console

:paperclip:

Screenshot / demo - agent in action

:paperclip:

Screenshot / demo from the website

Links


:sparkles: I just finished the Neo4j course and I'm so excited for the free credits! I wish I could have built a full-on agent, but I only started taking the courses last week. While I've built a RAG pipeline before as part of an art project to spread awareness about domestic violence, I'm still getting familiar with this specific workflow. With that said, I am SO excited :star_struck: to see what others have built and I hope Neo4j comes out with more competitions like this in the future! :sparkles:

@ari_Neo4j Just to clarify, because I may have gotten ahead of myself when I said I was happy to have earned credits, do we need to submit a screenshot of our agent? Mine is really basic at the moment, and I feel a wee bit ashamed. I was only working with the Northwind Dataset (while at the same time realizing that I only just started taking courses with Neo4j last week). Also, do we actually know how many people have been issued credits???

My Aura Hackathon Submission: Art Provenance Agent

What it does

Art Provenanve agent tracks the ownership changes and location of artworks. It can help research and answer queries about origin and transfers of artwork.

Dataset and why a graph fits

Datasets : It uses publicly available art provenance data from galleries and google sheets.

Why a graph fits

Graph is needed here to easily represent and query chains of ownership. And to find the key players in art network.

Agent Demo

Future Work

Include data for art loans. Museum displays.

Graph ML to identify key clusters and players in art network.

Graph can be used for multiple purposes including creator network to communicate to partons of their new art.

:brain: Agent Submission Details

:label: Agent Name

Outbreak Analysis


:bar_chart: What it does

The Outbreak Analysis Agent is a Neo4j Aura agent for analyzing Hantavirus (including Andes virus) outbreak data stored in a graph database.

It is used to explore and understand epidemiological patterns in the data, including:

  • Disease spread across countries and years
  • Outbreak hotspots and high-risk regions
  • Mortality rates and Case Fatality Rates (CFR)
  • Environmental factors like climate and rodent density
  • Virus strain behavior, including Andes virus transmission
  • Trends and anomalies in outbreak data

The agent uses Text2Cypher, Cypher templates, and graph relationships to answer both simple and complex questions.


:dna: Dataset and why a graph fits

The dataset is a Hantavirus (Andes Virus) global epidemiology dataset that includes:

  • Country-wise outbreak data (1993–2026)
  • Monthly case trends
  • Major outbreak events
  • Clinical outcomes (severity, deaths, recovery)
  • Environmental risk factors
  • Virus strain information (including Andes virus variants)

This data works well in a graph because the information is connected:

  • Countries are linked to outbreaks
  • Outbreaks are linked to virus strains
  • Outbreaks are linked to environmental factors
  • Clinical outcomes are tied to outbreaks
  • Time-based data connects outbreaks across years and months

A graph database like Neo4j is useful here because:

  • It supports relationship-based analysis

  • It makes it easier to follow connections between entities

  • It helps compare outbreaks across regions and time

  • It allows quick traversal across connected data without complex joins

  • It is suitable for modeling disease spread as a network

    Final Takeaway
    I was able to build a Neo4j Aura agent that connects and analyzes Hantavirus outbreak data using a graph structure. By creating relationships between Region, Month, and OutbreakEvent nodes, the agent can now run queries faster and provide more meaningful insights than a flat dataset. This setup makes it easier to explore trends, compare regions, and analyze outbreak patterns efficiently.

My Course completion : Building Agents in Neo4j Aura | Vigneshwaran S's Achievements | Free Neo4j Courses from GraphAcademy

Feel free to DM on this.